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
aaclayton
changed the title
Evaluate deprecation of socket.io library in favor of move to native client-side WebSocket interface.
Deprecate the socket.io library in favor of move to native client-side WebSocket interface.
Nov 6, 2022
aaclayton
added
api
Issues related to the API used by Mod Devs
and removed
epic
Major issues which represent substantial chunks of work
labels
Jul 17, 2023
I'm sure you're pretty versed on websockets but thought I'd post some relevant info. While websockets are commonly native now they would still lack two important features socket.io offers. These would need to be implemented personally:
Auto reconnects (using heartbeats)
packet buffering (packets are resent on re-connection).
Yes, absolutely right. These features (and also especially acknowledgements) are key to our use case. It's possible we will deprioritize this (again) as we have for previous versions because making this change is not an urgent need and we have plenty of other things that require doing in V12.
We may be able to eliminate the client-side socket.io client in favor of native
WebSocket
integration.This would require implementing a few bespoke features where we currently rely on Socket.io: https://socket.io/docs/v4/#features
The text was updated successfully, but these errors were encountered: