Skip to content
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

handling close or error message #3

Open
Chat-Wane opened this issue Nov 21, 2014 · 1 comment
Open

handling close or error message #3

Chat-Wane opened this issue Nov 21, 2014 · 1 comment

Comments

@Chat-Wane
Copy link
Owner

Currently, when a peer leaves the network (because crashes or voluntarily quits), no change are made in partialView and inView.
Thus, broadcasting generates errors because it cannot reach the peer.

Without implementing specifically the SCAMP protocol for this kind of situation (i.e. rebalancing and so on), at least, the peer must be delete from the views.

@Chat-Wane
Copy link
Owner Author

When WebRTC connections fail or close, it triggers event "close" or "error" ( Not sure about the error one, though ). Currently, it only remove the link from the view. However, the paper shows a better way to handle unsubscription in order to keep the network graph connected an balanced.

TODO: the unsubscription protocol, which requires that the user does not close directly the webpage. Such event would be considered as a crash.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant