Refactor AcBinary streaming: multi-message protocol - Renamed framing flags to multiMessage for clarity in AsyncPipeReaderInput/AsyncPipeWriterOutput. - Multi-message mode ([202]=end-of-message) now auto-resets input for reuse; session end is explicit. - Updated framing state machine, buffer cycling, and sentinel logic. - Revised all serializer/deserializer entry points and tests for new protocol. - Expanded docs and XML comments to detail wire format and protocol constraints. - Updated benchmarks and tests for new streaming API and multi-message behavior. - Documented protocol limits and added security issue/TODO for type-name deserialization in SignalR binary protocol. |
||
|---|---|---|
| .. | ||
| LOGGING | ||
| SIGNALR | ||
| SIGNALR_BINARY_PROTOCOL | ||
| adr | ||
| README.md | ||
README.md
AyCode.Services documentation
Topic documentation for the AyCode.Services project (Layer 0, service abstractions).
Topics
LOGGING/— Remote logger (variant — sends log entries over the wire)SIGNALR/— SignalR transport (tag-based protocol, generic hub methods)SIGNALR_BINARY_PROTOCOL/— Binary-over-SignalR wire format, chunked framing
Navigation
Per the AI Agent Core Protocol (folder navigation rule), start from this README when browsing docs/. Each topic folder has its own README.md with the main content, plus optional TOPIC_ISSUES.md (known issues) and TOPIC_TODO.md (planned work).
See also
- Base logger (framework):
../../AyCode.Core/AyCode.Core/docs/LOGGING/README.md - Server-side logger (variant):
../../AyCode.Core.Server/docs/LOGGING/README.md - Server-side SignalR:
../../AyCode.Services.Server/docs/SIGNALR/README.md - Server-side SignalR DataSource:
../../AyCode.Services.Server/docs/SIGNALR_DATASOURCE/README.md - Binary serializer (used by SIGNALR_BINARY_PROTOCOL):
../../AyCode.Core/AyCode.Core/docs/BINARY/README.md