Namespace DotBoxD.Services.Server
Classes
Section titled “Classes”Default DotBoxD.Services.Server.IInstanceRegistry. Backed by a single
System.Collections.Concurrent.ConcurrentDictionary keyed on
(serviceName, instanceId). One registry per connection.
Accepts connections from a listener and turns each one into an DotBoxD.Services.Peer.RpcPeer. The
accept loop that used to live inside the server now lives here, and its output is peers:
because each connection is a full peer, a host can both provide services to and call back
into the peers that connect to it.
Interfaces
Section titled “Interfaces”Per-connection registry that holds server-side sub-service instances by opaque instance identifier. Created by the server when a connection is accepted and drained when the connection closes — instances therefore have connection-scoped lifetime and cannot leak across tenants.
INonStreamingServiceDispatcher
Marker for dispatchers whose methods cannot consume streamed arguments or produce streamed responses. The peer can use this to skip allocating a streaming context for ordinary RPC calls.
The call surface a generated proxy uses to invoke methods the other side provides.
Implemented by DotBoxD.Services.Peer.RpcPeer. This is the transport-agnostic invoke
contract with no notion of “client” or “connect” — a peer simply forwards calls.
Interface for generated service dispatchers that route incoming requests to the
appropriate service method. Root-service dispatchers use DispatchAsync;
sub-service dispatchers also implement DispatchOnInstanceAsync to route
calls to a particular registered instance.