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
Disregarding all discussion above, a first point to address is the ability for a user to reconnect to osu-server-spectator. Regardless of whether we move responsibilities around, we need to ensure that a dropped websocket connection is not the end of the world for multiplayer, spectator, and (currently) replay storage.
Once we have this in place, we can decide whether responsibilities need to be shuffled.
The key part for the issue above is spectating flows, as they are the ones that implicitly participate in submission to upload replays. This will likely require a reconciliation flow which ensures that the client resends any frames the server might not have received.
The rest is also important for other reasons, but strictly speaking not for the aforementioned issue.
The text was updated successfully, but these errors were encountered:
Disregarding all discussion above, a first point to address is the ability for a user to reconnect to
osu-server-spectator
. Regardless of whether we move responsibilities around, we need to ensure that a dropped websocket connection is not the end of the world for multiplayer, spectator, and (currently) replay storage.Once we have this in place, we can decide whether responsibilities need to be shuffled.
Originally posted by @peppy in ppy/osu#24609 (comment)
The key part for the issue above is spectating flows, as they are the ones that implicitly participate in submission to upload replays. This will likely require a reconciliation flow which ensures that the client resends any frames the server might not have received.
The rest is also important for other reasons, but strictly speaking not for the aforementioned issue.
The text was updated successfully, but these errors were encountered: