Add bulk MXAccess subscription commands
This commit is contained in:
@@ -10,6 +10,19 @@ recreated by the contracts project build.
|
||||
`MxAccessGateway` gRPC service, command payloads, command replies, event DTOs,
|
||||
`MxValue`, `MxArray`, and `MxStatusProxy`.
|
||||
|
||||
The public command model includes bulk subscription command kinds for
|
||||
`AddItemBulk`, `AdviseItemBulk`, `RemoveItemBulk`, `UnAdviseItemBulk`,
|
||||
`SubscribeBulk`, and `UnsubscribeBulk`. These commands are normal unary
|
||||
`Invoke` payloads. They do not add separate gRPC methods, and they return a
|
||||
`BulkSubscribeReply` containing per-item `SubscribeResult` records with
|
||||
`ServerHandle`, `TagAddress`, `ItemHandle`, `WasSuccessful`, and
|
||||
`ErrorMessage`.
|
||||
|
||||
The gateway forwards each bulk command as one worker command. The worker runs
|
||||
the corresponding MXAccess `AddItem`, `Advise`, `UnAdvise`, and `RemoveItem`
|
||||
calls sequentially on the session STA and preserves input order in the result
|
||||
list.
|
||||
|
||||
`src/MxGateway.Contracts/Protos/mxaccess_worker.proto` defines the named-pipe
|
||||
worker IPC envelope and control messages. It imports
|
||||
`mxaccess_gateway.proto` so the worker and gateway use the same command, reply,
|
||||
|
||||
Reference in New Issue
Block a user