v1.3.4

This release only has test fixes. It's published because sharedb-mongo includes and runs the tests from sharedb.

• #368 - Fix test for sync unsubscribe, to work with sharedb-mongo (@ericyhwang)

v1.3.3

• #358 — Rewrite subscribe/unsubscribe logic (@alecgibson)
  • Should now correctly unsubscribe if calling subscribe then unsubscribe synchronously.
  • Only ever one subscribe or unsubscribe request inflight at a time
• #363 — fix textarea example (@alecgibson)

v1.3.2

#356 — fix presence resubscribe after destroy (@alecgibson)

v1.3.1

• #352 - Upgrade to async@2 (@ericyhwang)

v1.3.0

• #322 — Add Presence functionality (@gkubisa, @curran, @alecgibson)
  • Warning - This current presence implementation may not scale to hundreds of subscribed clients on a given doc, as a new client subscribing to presence for a doc will request presence data from all other clients subscribed to presence on that doc.
  • To enable presence handling for a server, pass options.presence: true to the ShareDB Backend constructor.
  • See README
  • Also see the presence example

v1.2.1

• #347 - Handshake immediately if socket is already open (@dead-horse)
  • This only applies to the new handshake mechanism added in 1.2.0

v1.2.0

• #341 - Add basic handshake negotiation and stable op src for clients across reconnects (@alecgibson)
  • In sharedb <= 1.1.0, a client gets a new server-generated connection.id each time it reconnects to another server. This means each reconnection results in the client's ops having a new src id and seq numbers that begin anew from 1.
  • 1.2.0+ clients connecting to 1.2.0+ servers will now keep their first connection.id across reconnections. On server agents, this is available as agent.src. The legacy server-generated id is still available as agent.clientId.
  • This change is compatible both ways. Old clients can still connect to new servers. New clients can still connect to old servers, though if a a new client connects to an older server, it will change to the server-generated connection.id.

v1.1.0

• #331 - Add ability for "readSnapshots" middleware to reject reads of specific snapshots, mainly for bulk fetch/subscribe (@ericyhwang)
  • context.rejectSnapshotRead(snapshot: Snapshot, error: Error | string) - Reject a specific snapshot read
  • context.rejectSnapshotReadSilent(snapshot: Snapshot, errorMessage: string) - As above, but causes the ShareDB client to treat it as a silent rejection, not passing the error back to user code

v1.0.0-beta.31

This 1.0.0-beta release adds client forwards compatibility with the new error codes in the final 1.0.0 release.

• c856ab7

See the upgrade guide for more details.

v1.0.0-beta.30

• #327 - Fix previously inflight op getting mutated if client disconnects (@Calyhre)