# implementing Published articles for implementing. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Implementing LFU Cache in O(1) Time: A Hands-on Breakdown DevFeed: [Implementing LFU Cache in O(1) Time: A Hands-on Breakdown]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-08-02T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Cache](), [Caching](), [Data structures](), [implementation]() Tags: [algorithms](), [cache](), [caching](), [implementing](), [java](), [lfu](), [memory](), [order](), [performance](), [pointers](), [system-design]() ### AI overview This tutorial explains why LRU can evict a frequently requested product during a long-tail burst, then presents an O(1) LFU cache design. It contrasts a naive O(n) eviction scan with an implementation using key-to-node and frequency-to-bucket maps, doubly linked lists, and a minFreq pointer. ### Source excerpt LFU evicts the least frequently used key rather than the least recently used, which protects a hot key during a long-tail burst that would make LRU drop a bestseller. The naive implementation scans every key to find the minimum frequency, which is O(n) per eviction. The O(1) version inverts the index: a key-to-node map, a frequency-to-bucket map of doubly linked lists, and a minFreq pointer. ## \[GSoC 2026\] Modernizing Haiku's Bluetooth stack: Implementing support for HFP profile - Mid-Term Progress Report DevFeed: [\[GSoC 2026\] Modernizing Haiku's Bluetooth stack: Implementing support for HFP profile - Mid-Term Progress Report]() Original publisher: [Read original article]() Author: vighnesh-sawant Published: 2026-07-15T14:32:12Z Content type: article Language: en Sources: [Haiku Project]() Topics: [Bluetooth](), [Protocol (disambiguation)](), [systems](), [real-time](), [Streaming](), [USB](), [Kernel](), [interface]() Tags: [api](), [bluetooth](), [driver](), [gsoc](), [haiku](), [implementing](), [kernel](), [modernizing](), [progress-report](), [protocol](), [real-time](), [report](), [software](), [streaming](), [usb]() ### AI overview A GSoC 2026 progress report on modernizing Haiku's Bluetooth stack by adding groundwork for the Hands-Free Profile. Completed work includes isochronous USB endpoint support, SCO handling, kernel hooks, and SCO and RFCOMM protocol implementations. Planned work covers SPP, SDP, and the remaining HFP functionality. ### Source excerpt Introduction Hello again! It has been a fun journey since the beginning of GSoC. My project focuses on modernizing Haiku's Bluetooth stack, specifically adding support for the Hands-Free Profile (HFP). HFP is a profile that allows operating systems to interact with Bluetooth audio devices, such as headsets, for two-way voice calls and audio streaming. Today, I'll be sharing a progress report on the work I have completed till now, and will outline my plans for the remainder of the project. Progress So Far A significant portion of my work has been dedicated to laying the groundwork for the HFP profile. Because Haiku's Bluetooth stack previously lacked the necessary transport layers for real-time audio, I had to implement several underlying protocols. Here is a breakdown of the changes I've made: USB and Driver Support (Isochronous Endpoints): I started off by adding support for isochronous USB endpoints to the h2generic Bluetooth driver. Isochronous transfers are critical because they guarantee bandwidth and timely delivery of data, which is a requirement for streaming real-time audio. Following this, I implemented SCO (Synchronous Connection-Oriented) handling within h2transactions, along with the proper scheduling mechanism.. Kernel Hooks: I added the necessary hooks for SCO and HCI (Host Controller Interface) commands. Protocol Implementations (SCO and RFCOMM): I successfully added the core implementations for both the SCO and RFCOMM protocols. RFCOMM provides an emulated serial interface over L2CAP. It serves as the control channel for many higher-level profiles, including HFP. SCO handles the actual low-latency audio transmission needed for voice calls. What's Next? Short-term Goals: Serial Port Profile (SPP) The Serial Port Profile sits on top of RFCOMM and provides a standard way to send and receive data. Implement SPP API: I will be implementing the JSR82 API methods for SPP in the Bluetooth kit. Implementing the Hands-Free Profile (HFP) The remaining time wil ## Reasoning about asyncio.Semaphore DevFeed: [Reasoning about asyncio.Semaphore]() Original publisher: [Read original article]() Author: Guido van Rossum (noreply@blogger.com) Published: 2022-10-05T06:39:00Z Content type: article Language: en Sources: [Guido van Rossum]() Topics: [Concurrency](), [Concurrent Programming](), [await]() Tags: [await](), [fairness](), [implementing](), [performance](), [reasoning](), [semantics](), [synchronization]() ### AI overview The article explains asyncio synchronization primitives through a restaurant queuing analogy. It maps exclusive access and cancellation to a Lock, then explains why multiple concurrently seated guests require a Semaphore. It also discusses challenges involving fairness, correctness, semantics, and performance. ### Source excerpt In Silicon Valley is a very exclusive fast-food restaurant, which is always open. There is one table, where one guest at a time is served an absolutely fabulous hamburger. When you arrive, you wait in line until the table is available. Then the host takes you to the table and, this being America, you are asked a seemingly endless series of questions about how you would like your hamburger to be cooked and served. But today we're not talking about culinary delights. We're talking about the queuing system used by the restaurant. If you are lucky to arrive at the restaurant when the table is available and there are no other guests waiting, you are seated right away. Otherwise, the host gives you a buzzer (from an infinite stack of buzzers!) and you are free to roam the neighborhood until your buzzer goes off. It is the host's job to ensure that guests are seated in order of arrival. When it is your turn, the host will cause your buzzer go off and you make your way back to the restaurant, where you will be seated. If you change your mind, you can return the buzzer to the host, who will take it back without lifting an eyebrow. If your buzzer has already gone off, the host will buzz the next guest, if any. Guests are always polite and don't abscond with their buzzers. The host is always fair and doesn't seat another guest ahead of you even if you take your time making it back. The above description fits that of a Lock. A guest arriving corresponds to the acquire() call; leaving is a release() call. Changing your mind is like getting cancelled while waiting in acquire(). You can change your mind before or after your buzzer goes off, i.e., you can be cancelled before or after the lock has awakened your call (but before you return from acquire()). One day the restaurant expands, hiring extra sous-chefs and opening several new tables. There is still only one host, whose job is not really changed. However, since multiple guests can be seated concurrently, a Semaphore must now ## Implementing Rich Results in a Content Management System (CMS): A Guide for Bartholomew CMS Users DevFeed: [Implementing Rich Results in a Content Management System (CMS): A Guide for Bartholomew CMS Users]() Original publisher: [Read original article]() Author: Tim McCallum Published: 2022-08-24T00:00:00Z Content type: tutorial Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Content Management System]() Tags: [cms](), [content](), [guide](), [how-to](), [implementing]() ### AI overview A guide to implementing rich results in Fermyon's Bartholomew Content Management System, including support for videos, images, and events beyond standard blue links. ### Source excerpt Rich results go beyond the standard blue link, helping to represent videos, images, events and more. This blog post shows how to implement rich results inside Fermyon's Content Management System (CMS) called Bartholomew. ## Implementing Stable API for Apache Airflow DevFeed: [Implementing Stable API for Apache Airflow]() Original publisher: [Read original article]() Author: Apache Airflow Published: 2020-07-19T00:00:00Z Content type: article Language: en Sources: [Apache Airflow Blog]() Topics: [REST API](), [OpenAPI Specification](), [API](), [Database](), [unit tests](), [Flask]() Tags: [apache-airflow](), [api](), [implementing](), [openapi](), [rest-api](), [schema](), [tests]() ### AI overview An Outreachy intern describes progress on extending and improving the Apache Airflow REST API. The article covers read-only Connection and DagRun endpoints, database schema work with Marshmallow 2, unit tests, OpenAPI date-time validation, and workarounds for library licensing and parsing issues. ### Source excerpt My Outreachy internship is coming to its ends which is also the best time to look back and reflect on the progress so far. The goal of my project is to Extend and Improve the Apache Airflow REST API. In this post, I will be sharing my progress so far. We started a bit late implementing the REST API because it took time for the OpenAPI 3.0 specification we were to use for the project to be merged. Thanks to Kamil, who paved the way for us to start implementing the REST API endpoints. Below are the endpoints I implemented and the challenges I encountered, including how I overcame them. Implementing The Read-Only Connection Endpoints The read-only connection endpoints were the first endpoint I implemented. Looking back, I can see how much I have improved. I started by implementing the database schema for the Connection table using Marshmallow 2. We had to use Marshmallow 2 because Flask-AppBuilder was still using it and Flask-AppBuilder is deeply integrated to Apache Airflow. This meant I had to unlearn Marshmallow 3 that I had been studying before this realization, but thankfully, Marshmallow 3 isn't too different, so I was able to start using Marshmallow 2 in no time. This first PR would have been more difficult than it was unless there had been any reference endpoint to look at. Kamil implemented a draft PR in which I took inspiration from. Thanks to this, It was easy for me to write the unit tests. It was also in this endpoint that I learned using parameterized in unit tests :D. Implementing The Read-Only DagRuns Endpoints This endpoint came with its many challenges, especially on filtering with datetimes. This was because the connexion library we were using to build the REST API was not validating date-time format in OpenAPI 3.0 specification, what I eventually found out, was intentional. Connexion dropped strict-rfc3339 because of the later license which is not compatible with Apache 2.0 license. I implemented a workaround on this, by defining a function called c ## Implementing mouse pointer interactions on iPad DevFeed: [Implementing mouse pointer interactions on iPad]() Original publisher: [Read original article]() Published: 2020-03-24T21:00:00Z Content type: tutorial Language: en Sources: [Rambo Codes]() Topics: [iOS](), [ui](), [coding](), [GUI](), [Xcode](), [keyboard]() Tags: [animations](), [apple](), [coding](), [gui](), [implementing](), [interaction](), [ios](), [ipad](), [keyboard](), [sdk]() ### AI overview A guide to implementing mouse and trackpad pointer interactions on iPadOS 13.4. It covers the relevant APIs, setup requirements, UIHoverGestureRecognizer, and hover animations while noting that iPad pointer behavior differs from macOS. ### Source excerpt Gui Rambo writes about his coding and reverse engineering adventures. ## Implementing Critical CSS on your website DevFeed: [Implementing Critical CSS on your website]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-02-28T21:34:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [modern web development](), [Web Development](), [Front end](), [inlining](), [render](), [Website]() Tags: [article](), [browser](), [critical](), [development](), [essential](), [frontend](), [how-to](), [implementing](), [inlining](), [insights](), [modern](), [modern-web-development](), [performant](), [render](), [shows](), [website]() ### AI overview This tutorial explains Critical CSS, a method for extracting the CSS needed for above-the-fold content and inlining it so the browser can render the page immediately. It presents the technique as part of building performant websites. ### Source excerpt Implementing Critical CSS is an essential part of modern website development, this article shows you how to do it ## Implementing multimethods in Python DevFeed: [Implementing multimethods in Python]() Original publisher: [Read original article]() Published: 2014-12-11T00:00:00Z Content type: tutorial Language: en Sources: [Adam Bard]() Topics: [Python](), [Clojure](), [implementation](), [function]() Tags: [clojure](), [code](), [function](), [implementation](), [implementing](), [library](), [monkey-patching](), [production](), [python](), [test](), [use-cases]() ### AI overview This article explains multimethods in Python as an implementation of multiple dispatch. It contrasts user-defined dispatch on arbitrary values with conventional single dispatch based on an argument's type, and discusses use cases such as reducing nested conditionals, extending existing classes, and dispatching on dictionary keys. ### Source excerpt In Clojure (and many other languages), a multimethod is an implementation of multiple dispatch as an alternative to single dispatch. Traditionally, if you define several methods with the same name on different classes, the type/class of the first argument (in Python, self, in many other languages implicit) is used to pick which method to call. This is called "single dispatch" because the decision of which method to call is left up to the inferred type of a single argument. Multimethods take the approach of leaving the dispatch up to the user; you can dispatch on any value at all. You just need to supply a function that returns the value on which you wish to dispatch, and a method for each possible value. For certain cases, this is a lot more flexible than single dispatch. ## ReactOS TODO update: explorer-new activation and window handling fixes DevFeed: [ReactOS TODO update: explorer-new activation and window handling fixes]() Original publisher: [Read original article]() Published: 2014-05-26T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [Shell](), [Windows](), [opensource]() Tags: [existing](), [free](), [implementing](), [issue](), [open-source](), [opensource](), [os](), [react](), [reactos](), [shell](), [win32](), [winapi](), [windows]() ### AI overview A ReactOS development report describes a patch fixing an activation issue and explains a workaround for explorer-new launching new explorer.exe instances when opening folders. The underlying DDE handler issue remains unresolved. ### Source excerpt If you recall from the last report, I had a few issues that I couldn't fix myself. Well, Huw (Frontier) surprised me by sending me a patch to fix the activation issue! One of the issues in explorer-new was that every time you clicked on the desktop to open a new folder, it would launch a new instance of explorer.exe and run the new window on it. While the underlying issue still remains (it requires implementing the DDE handler for explorer), by disabling the version of the desktop window from RShell and using the existing one from shell32 instead, the shell takes a shortcut and runs the window directly on its own instance. ## Introducing Elliptic Curves DevFeed: [Introducing Elliptic Curves]() Original publisher: [Read original article]() Published: 2014-02-08T10:00:14Z Content type: tutorial Language: en Sources: [Jeremy Kun]() Topics: [Cryptography](), [Programming](), [Algorithms, Complexity](), [Encryption]() Tags: [cryptography](), [diffie-hellman](), [digital-signatures](), [elliptic-curves](), [encryption](), [implementing](), [nsa](), [python](), [rsa]() ### AI overview An introductory tutorial series on elliptic curves and elliptic curve cryptography. It explains the motivation for ECC, its relationship to RSA and cryptographic security, and plans implementations covering finite fields, key exchange, encryption, and digital signatures. ### Source excerpt With all the recent revelations of government spying and backdoors into cryptographic standards, I am starting to disagree with the argument that you should never roll your own cryptography. Of course there are massive pitfalls and very few people actually need home-brewed cryptography, but history has made it clear that blindly accepting the word of the experts is not an acceptable course of action. What we really need is more understanding of cryptography, and implementing the algorithms yourself is the best way to do that. ## Dynamic Triggers in PLpgSQL DevFeed: [Dynamic Triggers in PLpgSQL]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2010-11-24T15:45:00Z Content type: tutorial Language: en Sources: [Dimitri Fontaine]() Topics: [Code](), [function]() Tags: [code](), [developer](), [function](), [implementing](), [triggers]() ### AI overview This article explores implementing dynamic triggers in PL/pgSQL, including reusing the same trigger function across multiple tables and handling a dynamic column name. The author describes the approach as difficult, unconventional, and preliminary, with slow performance in initial tests. ### Source excerpt You certainly know that implementing dynamic triggers in PLpgSQL is impossible. But I had a very bad night, being up from as soon as 3:30 am today, so that when a developer asked me about reusing the same trigger function code from more than one table and for a dynamic column name, I didn't remember about it being impossible. Here's what happens in such cases, after a long time on the problem (yes, overall, that's a slow day). Note that I'm abusing the (record_literal).* notation a lot in there, and even the (record_literal).column_name too.