mirror of
https://github.com/ppy/osu.git
synced 2024-12-14 08:33:21 +08:00
b4aa247032
First of all, this sort of cleanup isn't really the client's responsibility, and secondly, at the point the client received this request to disconnect, *none of its requests will be honored anymore* (currently the only scenario of this if another client has connected - the server-side concurrency filter will reject this request). When disconnection is requested, the only valid thing to do with respect to talking to the server is to stop doing it. This will be moved server-side in a follow-up change, although I'm not even strictly sure that's required - I'd like to think signalr would know to clean up a disconnecting client from all groups they were in. |
||
---|---|---|
.. | ||
API | ||
Chat | ||
Leaderboards | ||
Metadata | ||
Multiplayer | ||
Notifications/WebSocket | ||
Placeholders | ||
Rooms | ||
Solo | ||
Spectator | ||
BeatmapDownloadTracker.cs | ||
DevelopmentEndpointConfiguration.cs | ||
DownloadState.cs | ||
DownloadTracker.cs | ||
EndpointConfiguration.cs | ||
HubClient.cs | ||
HubClientConnector.cs | ||
IHubClientConnector.cs | ||
ILinkHandler.cs | ||
IStatefulUserHubClient.cs | ||
OnlineStatusNotifier.cs | ||
OnlineViewContainer.cs | ||
PersistentEndpointClient.cs | ||
PersistentEndpointClientConnector.cs | ||
PollingComponent.cs | ||
ProductionEndpointConfiguration.cs | ||
ScoreDownloadTracker.cs | ||
SignalRDerivedTypeWorkaroundJsonConverter.cs | ||
SignalRUnionWorkaroundResolver.cs | ||
SignalRWorkaroundTypes.cs |