@gajae-code/bridge-client 0.13.3 exposes onFrame, onReconnect, onReconnectFailed, send, request, and control, but no instance-scoped transport close/error subscription.
A consumer that must synchronously mark the post-send dispatch boundary cannot use control()/request() directly: those APIs correctly retire pending requests on socket closure but do not expose the send-boundary callback. Its only alternative is a raw send() + onFrame() request, which cannot settle when the socket closes after send and before response; it waits until timeout.
Please expose one of:
- an instance-scoped close/error subscription that settles for the active transport generation; or
- a dispatch-aware request/control API with
beforeDispatch/onDispatch callbacks while preserving the released client's pending-request retirement behavior.
The callback must fire synchronously after the frame handoff, and all close/error/reconnect cleanup must remain generation-safe.
Downstream report: snowykr/openwebui-gjc-adapter#34
@gajae-code/bridge-client0.13.3 exposesonFrame,onReconnect,onReconnectFailed,send,request, andcontrol, but no instance-scoped transport close/error subscription.A consumer that must synchronously mark the post-
senddispatch boundary cannot usecontrol()/request()directly: those APIs correctly retire pending requests on socket closure but do not expose the send-boundary callback. Its only alternative is a rawsend()+onFrame()request, which cannot settle when the socket closes after send and before response; it waits until timeout.Please expose one of:
beforeDispatch/onDispatchcallbacks while preserving the released client's pending-request retirement behavior.The callback must fire synchronously after the frame handoff, and all close/error/reconnect cleanup must remain generation-safe.
Downstream report: snowykr/openwebui-gjc-adapter#34