Issue #13: implement public grpc service

2026-04-26 17:42:38 -04:00
parent 626e7762d9
commit 8d6d3f6188
8 changed files with 962 additions and 2 deletions
@@ -852,6 +852,14 @@ The gRPC layer should be thin:
 Avoid embedding MXAccess-specific business logic in gRPC handlers. Keep the
 translation code testable.

+The gateway maps `MxAccessGateway` to `MxAccessGatewayService`. The service
+implements `OpenSession`, `CloseSession`, `Invoke`, and `StreamEvents` by
+validating public requests, delegating session work to `ISessionManager`, and
+using explicit mapper code for public-to-worker commands, worker replies, and
+events. Missing sessions and transport failures return gRPC status errors;
+worker command replies preserve MXAccess HRESULT and status details in the
+public reply.
+
 ## C# Worker Versus C++ Worker

 Start with a C# .NET Framework 4.8 x86 worker.