60 lines
6.0 KiB
Markdown
60 lines
6.0 KiB
Markdown
# LmxProxy v2 Rebuild — Deviations & Key Technical Decisions
|
||
|
||
Decisions made during implementation that differ from or extend the original plan.
|
||
|
||
## 1. Grpc.Tools downgraded to 2.68.1
|
||
|
||
**Plan specified**: Grpc.Tools 2.71.0
|
||
**Actual**: 2.68.1
|
||
**Why**: protoc.exe from 2.71.0 crashes with access violation (exit code 0xC0000005) on windev (Windows 10, x64). The 2.68.1 version works reliably.
|
||
**How to apply**: If upgrading Grpc.Tools in the future, test protoc on windev first.
|
||
|
||
## 2. STA Dispatch Thread replaced with Task.Run
|
||
|
||
**Plan specified**: Dedicated STA thread with `BlockingCollection<Action>` dispatch queue and `Application.DoEvents()` message pump for all COM operations.
|
||
**Actual**: `Task.Run` on thread pool (MTA) for all COM operations, matching the v1 pattern.
|
||
**Why**: The STA thread's message pump (`Application.DoEvents()`) between work items was insufficient — when a COM call like `AdviseSupervisory` was dispatched and the thread blocked waiting for the next work item, COM event callbacks (`OnDataChange`, `OnWriteComplete`) never fired because there was no active message pump during the wait. MxAccess works from MTA threads because COM marshaling handles cross-apartment calls, and events fire on their own threads.
|
||
**How to apply**: Do not reintroduce STA threading for MxAccess. The `System.Windows.Forms` reference was removed from the Host csproj.
|
||
|
||
## 3. TypedValue property-level `_setCase` tracking
|
||
|
||
**Plan specified**: `GetValueCase()` heuristic checking non-default values (e.g., `if (BoolValue) return BoolValue`).
|
||
**Actual**: Each property setter records `_setCase = TypedValueCase.XxxValue`, and `GetValueCase()` returns `_setCase` directly.
|
||
**Why**: protobuf-net code-first has no native `oneof` support. The heuristic approach can't distinguish "field not set" from "field set to default value" (e.g., `BoolValue = false`, `DoubleValue = 0.0`, `Int32Value = 0`). Since protobuf-net calls property setters during deserialization, tracking in the setter correctly identifies which field was deserialized.
|
||
**How to apply**: Always use `GetValueCase()` to determine which TypedValue field is set, never check for non-default values directly.
|
||
|
||
## 4. API key sent via HTTP header (DelegatingHandler)
|
||
|
||
**Plan specified**: API key sent in `ConnectRequest.ApiKey` field (request body).
|
||
**Actual**: API key sent as `x-api-key` HTTP header on every gRPC request via `ApiKeyDelegatingHandler`, in addition to the request body.
|
||
**Why**: The Host's `ApiKeyInterceptor` validates the `x-api-key` gRPC metadata header before any RPC handler executes. protobuf-net.Grpc's `CreateGrpcService<T>()` doesn't expose per-call metadata, so the header must be added at the HTTP transport level. A `DelegatingHandler` wrapping the `SocketsHttpHandler` adds it to all outgoing requests.
|
||
**How to apply**: The `GrpcChannelFactory.CreateChannel()` accepts an optional `apiKey` parameter. The `LmxProxyClient` passes it during channel creation in `ConnectAsync`.
|
||
|
||
## 5. v2 test deployment on port 50100
|
||
|
||
**Plan specified**: Port 50052 for v2 test deployment.
|
||
**Actual**: Port 50100.
|
||
**Why**: Ports 50049–50060 are used by MxAccess internal COM connections (established TCP pairs between the COM client and server). Port 50052 was occupied by an ephemeral MxAccess connection from the v1 service.
|
||
**How to apply**: When deploying alongside v1, use ports above 50100 to avoid MxAccess ephemeral port range.
|
||
|
||
## 6. CheckApiKey validates request body key
|
||
|
||
**Plan specified**: Not explicitly defined — the interceptor validates the header key.
|
||
**Actual**: `CheckApiKey` RPC validates the key from the *request body* (`request.ApiKey`) against `ApiKeyService`, not the header key.
|
||
**Why**: The `x-api-key` header always carries the caller's valid key (for interceptor auth). The `CheckApiKey` RPC is designed for clients to test whether a *different* key is valid, so it must check the body key independently.
|
||
**How to apply**: `ScadaGrpcService` receives `ApiKeyService` as an optional constructor parameter.
|
||
|
||
## 7. Write completes synchronously (fire-and-forget)
|
||
|
||
**Plan specified**: Wait for `OnWriteComplete` COM callback to confirm write success.
|
||
**Actual**: Write is confirmed synchronously — if `_lmxProxy.Write()` returns without throwing, the write succeeded. The `OnWriteComplete` callback is kept wired for diagnostic logging only.
|
||
**Why**: MxAccess completes supervisory writes synchronously. The `OnWriteComplete` COM callback never fires for simple supervisory writes, causing the original implementation to timeout waiting for a callback that would never arrive. This caused WriteAndReadBack and WriteBatchAndWait integration tests to fail.
|
||
**How to apply**: Do not await `OnWriteComplete` for write confirmation. The `Write()` COM call succeeding (not throwing a COM exception) is the confirmation. Clean up (UnAdvise + RemoveItem) happens immediately after the write in a finally block.
|
||
|
||
## 8. SubscriptionManager must create MxAccess COM subscriptions
|
||
|
||
**Plan specified**: SubscriptionManager manages per-client channels and routes updates from MxAccess.
|
||
**Actual**: SubscriptionManager must also call `IScadaClient.SubscribeAsync()` to create the underlying COM subscriptions when a tag is first subscribed, and dispose them when the last client unsubscribes.
|
||
**Why**: The Phase 2 implementation tracked client-to-tag routing in internal dictionaries but never called `MxAccessClient.SubscribeAsync()` to create the actual MxAccess COM subscriptions (`AddItem` + `AdviseSupervisory`). Without the COM subscription, `OnDataChange` never fired and no updates were delivered to clients. This caused the `Subscribe_ReceivesUpdates` integration test to receive 0 updates over 30 seconds.
|
||
**How to apply**: `SubscriptionManager.Subscribe()` collects newly-seen tags (those without an existing `TagSubscription`) and calls `_scadaClient.SubscribeAsync()` for them, passing `OnTagValueChanged` as the callback. The returned `IAsyncDisposable` handles are tracked in `_mxAccessHandles` per address and disposed in `UnsubscribeClient()` when the last client for a tag leaves.
|