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 the SocketID has a generated prefix from one source. In order to allow custom prefixes the ID should contain two parts the ID and the Prefix. This way there can't be custom generators that can generate fake-able ID's in the system. The two parts could look like something as simple as:
type ID struct { prefix, id string }
This needs to be threaded throughout the system, and must convert to a String() for logging and debugging.
The text was updated successfully, but these errors were encountered:
njones
changed the title
Update the SocketID to work with a user defined prefix
socket-io: Update the SocketID to work with a user defined prefix
Jan 23, 2024
Currently the SocketID has a generated prefix from one source. In order to allow custom prefixes the ID should contain two parts the ID and the Prefix. This way there can't be custom generators that can generate fake-able ID's in the system. The two parts could look like something as simple as:
This needs to be threaded throughout the system, and must convert to a String() for logging and debugging.
The text was updated successfully, but these errors were encountered: