Joseph Doherty 467fdc34d8 docs(lmxproxy): correct deviation #7 — OnWriteComplete is a COM threading issue, not MxAccess behavior ...

The MxAccess docs explicitly state OnWriteComplete always fires after Write().
The real cause is no Windows message pump in the headless service process to
marshal the COM callback. Fire-and-forget is safe for supervisory writes but
would miss secured/verified write rejections (errors 1012/1013).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-22 04:53:54 -04:00

..

plans

docs(lmxproxy): update test tags to TestChildObject namespace for v2 type coverage

2026-03-21 23:35:15 -04:00

requirements

docs: add LmxProxy requirements documentation with v2 protocol as authoritative design

2026-03-21 22:38:11 -04:00

deviations.md

docs(lmxproxy): correct deviation #7 — OnWriteComplete is a COM threading issue, not MxAccess behavior

2026-03-22 04:53:54 -04:00

lmxproxy_protocol.md

feat: add standalone LmxProxy solution, windev VM documentation

2026-03-21 20:50:05 -04:00

lmxproxy_updates.md

feat: add standalone LmxProxy solution, windev VM documentation

2026-03-21 20:50:05 -04:00