- Move all major feature docs (logging, binary, SignalR, DataSource) into per-project `docs/` folders with dedicated Markdown files. - Split monolithic docs into focused files: `BINARY_FORMAT.md`, `BINARY_FEATURES.md`, `BINARY_OPTIONS.md`, `LOGGING.md`, `LOGGING_SERVER.md`, `LOGGING_REMOTE.md`, `SIGNALR.md`, `SIGNALR_SERVER.md`, `SIGNALR_DATASOURCE.md`. - Update all references in `README.md`, `copilot-instructions.md`, `GLOSSARY.md`, and `ARCHITECTURE.md` to point to the correct per-project doc. - Add documentation tables to each project’s `README.md` and clarify folder structure. - Update `.csproj` files to include `docs/**/*.md` for packaging. - Remove obsolete/moved docs from the solution file. - Ensure all technical debt warnings and cross-references are preserved and accurate. - No code changes; documentation only. |
||
|---|---|---|
| .. | ||
| AcLogItemClient.cs | ||
| README.md | ||
README.md
LogItems
Client-side log item entity used for structured logging. Serialized with MessagePack for efficient transport over SignalR.
For full logging architecture see
docs/LOGGING.md.
Key Files
AcLogItemClient.cs— ImplementsIAcLogItemClient.[MessagePackObject]with explicit key indices (5, 15, 20, 25, 30, 35, 40, 45, 50). Fields:TimeStampUtc,AppType,LogLevel,ThreadId,CategoryName,CallerName,Text,ErrorType,Exception. Extended byAcLogItemon the server side.