-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
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
[After TMM] Revise protocol documentation #482
Comments
how about implementing the hole protocol into a webassembly module, witch can be shared between the server and client ? |
I’m not sure how that would work. Can you elaborate? |
I am always surprised a little that the protocol was never defined in a third repo using like Google protobuf that allows it to be cross language |
https://webassembly.org/ |
We really need a dedicated server protocol document where we write down what messages are sent by the client, and what responses come from the server. That way the client developers can have something to reference without needing to read the server code. This would also push us toward defined protocol versions where we can explicitly say "version 1.0 has exactly these commands".
Ideally we would refactor the server so that much of this documentation could be generated automatically from doc strings.
The text was updated successfully, but these errors were encountered: