-
Marc Gravell authored
* start work on a true async write path (no sync flush); at the moment only existing async code uses this - once stable, we can move more code to the full async path * finish prep work before tackling subscriber lock (note: still lots of handshake options to asyncify) * implement a background queue that represents the (necessarily ordered) subscription operations, rather than executing them synchronously (sync over async, locks, etc)