We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It is hard to know if two client states are correct.
We need at least periodic messages with the frame number and state checksum to be verified by other peers.
If the validation fails, the client should be disconnected.
UPDATE: There is a started work on consistency-check branch.
The problem is, that the GetHashCode() approach for state validity it is not stable between different appdomains because it changes on every execution, so it necessary to rethink how we do checksum, and/or even how we are serializing the state data as most eligible checksum algorithm run on byte arrays (like Fletcher-32, CRC, etc).
GetHashCode()
The text was updated successfully, but these errors were encountered:
lucasteles
When branches are created from issues, their pull requests are automatically linked.
It is hard to know if two client states are correct.
We need at least periodic messages with the frame number and state checksum to be verified by other peers.
If the validation fails, the client should be disconnected.
UPDATE:
There is a started work on consistency-check branch.
The problem is, that the
GetHashCode()
approach for state validity it is not stable between different appdomains because it changes on every execution, so it necessary to rethink how we do checksum, and/or even how we are serializing the state data as most eligible checksum algorithm run on byte arrays (like Fletcher-32, CRC, etc).The text was updated successfully, but these errors were encountered: