You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: