History

Loretta 2d04b9f8f6 Zero-copy SignalR: direct object response, no SignalData Major overhaul for SignalR response pipeline: - All deserialization now uses byte[] (offset/length) for zero-copy, allocation-free operation; all span/memory overloads removed. - SignalR protocol sends (signalParams, object) directly; SignalData envelope and related logic removed. - Server sets SignalParams.SignalDataType so protocol deserializes to the correct runtime type on the client. - SignalResponseDataMessage now only used for client request/response tracking and stream path; RawResponseData holds the actual object. - All extension methods, helpers, and infrastructure updated to use new byte[]-based APIs. - AcSignalRDataSource and all test/benchmark code updated for new object flow. - Removes all diagnostics, logging, and error handling related to binary envelopes. - Enables true zero-copy, type-safe, allocation-free SignalR response handling.		2026-04-06 22:45:00 +02:00
..
Loggers	Update README links to use code-style paths for docs	2026-03-30 08:01:05 +02:00
Logins	Document AcBinary wire format, sync docs, update conventions	2026-03-29 09:11:57 +02:00
SignalRs	Zero-copy SignalR: direct object response, no SignalData	2026-04-06 22:45:00 +02:00
docs	Switch SignalR payloads to ArrayPool-backed SignalData	2026-04-06 11:17:02 +02:00
AyCode.Services.csproj	Refactor: Split and expand project-level documentation	2026-03-29 22:16:28 +02:00
README.md	Add structured metadata blocks to all project/repo docs	2026-03-30 08:53:56 +02:00

README.md

AyCode.Services

@project { type = "framework" }

Shared service implementations: SignalR communication (custom binary protocol), login services, and remote log writers.

Documentation

Document	Topic
`SIGNALR.md`	Client-side SignalR transport (tags, wire protocol, req/resp flow)
`LOGGING_REMOTE.md`	Remote log writers (HTTP, browser console, SignalR)

Folder Structure

Folder	Purpose
`Loggers/`	Remote log writers: HTTP, browser console (JS interop), SignalR
`Logins/`	Base and client-side login service implementations
`SignalRs/`	Custom binary SignalR protocol, client base, message tagging, serialization

Dependencies

Dependency	Purpose
`AyCode.Core`	Core types, serializers, compression
`AyCode.Entities`	Entity base classes
`AyCode.Interfaces`	Service contracts
`AyCode.Models`	DTOs
`Microsoft.AspNetCore.SignalR.Client`	SignalR client
`Microsoft.AspNetCore.SignalR.Common`	`IHubProtocol` for custom binary protocol
`Microsoft.AspNetCore.Authentication.JwtBearer`	JWT authentication