From 891990befae5c37dc643c4b86f473089ecf34aba Mon Sep 17 00:00:00 2001 From: Benoit Chesneau Date: Mon, 26 Jan 2026 09:39:46 +0100 Subject: [PATCH] docs(dirty): update streaming from future to current feature --- docs/content/dirty.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/dirty.md b/docs/content/dirty.md index c67a8bb8..583d3fbf 100644 --- a/docs/content/dirty.md +++ b/docs/content/dirty.md @@ -19,7 +19,7 @@ Dirty Arbiters solve this by providing: - **Stateful workers** - Loaded resources persist in dirty worker memory - **Message-passing IPC** - Communication via Unix sockets with JSON serialization - **Explicit API** - Clear `execute()` calls (no hidden IPC) -- **Asyncio-based** - Enables future streaming support and clean concurrent handling +- **Asyncio-based** - Clean concurrent handling with streaming support ## Design Philosophy @@ -44,7 +44,7 @@ The Dirty Arbiter uses asyncio for its core loop rather than the main arbiter's - **Non-blocking IPC** - Can handle many concurrent client connections efficiently - **Concurrent request routing** - Multiple requests can be dispatched to workers simultaneously -- **Future streaming** - Native support for async generators and streaming responses +- **Streaming support** - Native async generators for streaming responses - **Clean signal handling** - Signals integrate cleanly via `loop.add_signal_handler()` ### Stateful Applications