Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
Security Level: Public
-
None
-
5
Description
It's not easy to close a BlipSyncContext from the SG side - which causes us to ask the client to disconnect a replication by sending them a specific error code on any of the message repsonses (HTTP/503) in CBG-1878
This isn't ideal, and we'd like to have the ability to tear down a whole blipsync replication with a specific status code. Doing this might depend on updating the websocket library to support close handshakes.
Attachments
Issue Links
- depends on
-
CBG-1901 Update websocket implementation
- Closed