docs(dirty): update streaming from future to current feature

This commit is contained in:
Benoit Chesneau 2026-01-26 09:39:46 +01:00
parent 35559a87bd
commit 891990befa

View File

@ -19,7 +19,7 @@ Dirty Arbiters solve this by providing:
- **Stateful workers** - Loaded resources persist in dirty worker memory - **Stateful workers** - Loaded resources persist in dirty worker memory
- **Message-passing IPC** - Communication via Unix sockets with JSON serialization - **Message-passing IPC** - Communication via Unix sockets with JSON serialization
- **Explicit API** - Clear `execute()` calls (no hidden IPC) - **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 ## 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 - **Non-blocking IPC** - Can handle many concurrent client connections efficiently
- **Concurrent request routing** - Multiple requests can be dispatched to workers simultaneously - **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()` - **Clean signal handling** - Signals integrate cleanly via `loop.add_signal_handler()`
### Stateful Applications ### Stateful Applications