Future of Mesa #1
Description
There's a couple of features Mesa should have before being ready for use in @cryb/api and @cryb/web. This issue hopefully makes an outline of what needs to be integrated before this can take place.
-
Extract client to separate library
-
Migrate Dispatcher from sending messages via publishing to connecting as a special client
-
Better disconnection handling
-
Add timeout support for clustered reconnections (especially useful in Atlas)
-
Rate limiting support