Add ADR-0003: AcBinary streaming receive unification - Add cross-cutting ADR-0003 for AsyncPipeReaderInput and transport-agnostic streaming helpers (NamedPipe, FileStream) - Update BINARY and SIGNALR_BINARY_PROTOCOL docs to reference ADR-0003 - Add migration TODOs for each ADR-0003 step with acceptance criteria - Add project ADR-0001 (binary projection serialization) and index - Clarify buffer sizing and ADR refs in SegmentBufferReader docs - Migrate JWT key/token log issues from LOGGING to new AUTH topic per ADR - Update ADR template and improve doc formatting throughout |
||
|---|---|---|
| .. | ||
| 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