-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Realtime: there is no dedicated object to manage connections #36
Comments
Ok, this in itself is not necessarily an issue, however are you therefore implying that all of |
@mattheworiordan There is no Connection object either. The Realtime client instances a Transport object and connects to the server with the current WebSocket. Just one connection per client. |
@ricardopereira that is fine, other than the |
Well, the connection is handled on the |
BTW. What happens when the transport is closed & re-opened (such as connection failure), does the |
The object remains consistent. On Wednesday, 28 October 2015, mattheworiordan [email protected]
|
Ok, great, well lets go with a proxy object for now as that will allow us to meet the requirements of the spec easily |
No description provided.
The text was updated successfully, but these errors were encountered: