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
This may already exist, but I'm not sure where to request/ask about it. Is there a way to get a hash of all of the types that Netserializer knows about? The idea would be to use this as a 'protocol version', meaning that if it changes, the client and server are incompatible with each other. Since Netserializer is already going recursively though all of the types that we would possibly send over the wire, it seems like we could build a unique value that the two sides can use to verify they speak the exact same protocol.
Right now we require the client and server to be from exactly the same build, but it would be very useful to be able to verify that they're compatible without that requirement (while still ensuring that none of the messages / types involved in the protocol have been changed).
The text was updated successfully, but these errors were encountered:
This may already exist, but I'm not sure where to request/ask about it. Is there a way to get a hash of all of the types that Netserializer knows about? The idea would be to use this as a 'protocol version', meaning that if it changes, the client and server are incompatible with each other. Since Netserializer is already going recursively though all of the types that we would possibly send over the wire, it seems like we could build a unique value that the two sides can use to verify they speak the exact same protocol.
Right now we require the client and server to be from exactly the same build, but it would be very useful to be able to verify that they're compatible without that requirement (while still ensuring that none of the messages / types involved in the protocol have been changed).
The text was updated successfully, but these errors were encountered: