Hocuspocus 3

[janthurau]

• Separate the http server from the hocuspocus logic (WIP: refactor to separate server and hocuspocus (#686) #911)
• ⏳ Clean up connection handling (it was messy because we wanted to keep compatibility between v1 and v2)
• ⏳ Better error handling / reconnection logic (An authentication token is required, but you didn’t send one - but token was actually included #813)
• Update examples / docs:
• • always add onAuthenticateFailed, onClose, unsyncedChanges watchers
• • always pass a websocket separately and use provider.attach to avoid issues in strict mode

[julianpoy]

The subdocument ticket (#583) has the "next-major" tag on it. Will that be part of Hocuspocus v3?

[janthurau]

@julianpoy yjs-like subdocument support won't be included in v3, but you can utilize multiplexing and just split documents like documentId/main ; documentId/sub1 ; documentId/sub2, which gives you the same set of benefits.

[Palanikannan1437]

The issue with Multiplexing right now is that when the provider is destroyed (irrespective of what options are passed, the websocket connection is closed), even if I destroy it after a delay or something as @janthurau suggested in of the comments. Can we fix this?

[janthurau]

@Palanikannan1437 this is fixed in v3 - if you find time, it would be great if you could check it out :)

[Palanikannan1437]

Yess, I'll check this right away!! Thanks @janthurau !!

Could you help me out with how I could try the rc version out?

[branks]

Can you confirm what preserveConnection does in v3 please? It seems to only exist in the readme but none of the code?