Operational data
Receipts, sales, credit operations, cash operations, and QR payments.
PROJECT BRIEF / 30.07.2026
An HTTP integration gateway for operational data from 1C Retail, designed without write access to the information base.
The gateway accepts authenticated requests, passes them to a child process, and reaches V83.COMConnector. It serves receipts, sales, credit, cash operations, QR payments, and configuration knowledge.
Receipts, sales, credit operations, cash operations, and QR payments.
HMAC authentication, loopback child process, and read-only routes.
341 objects and 1,471 explicit links, with no runtime errors or truncated samples.
Health, metadata, runtime, diagnostics, and signed restart.
ThreadingHTTPServer permits parallel worker threads while OneCClient keeps cached COM state without visible serialization or thread-local ownership. The fake-COM harness reproduced a lazy-init race in 49 of 50 runs, duplicate connections, and overlapping COM calls.
Evidence of an architectural risk, not proof of a production incident: real V83.COMConnector has not yet had a controlled read-only probe.