Skip to content
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

Version the protocol #11

Open
rmg opened this issue Dec 3, 2014 · 0 comments
Open

Version the protocol #11

rmg opened this issue Dec 3, 2014 · 0 comments

Comments

@rmg
Copy link
Member

rmg commented Dec 3, 2014

Since the base protocol doesn't have any sort of handshake, each message should include a version field. We could use semver for the version comparison, but we would need to sort out how it is applied on the receiving side and sort out how a mismatch is communicated back to the sender and the code that the control channel is hosted in.

This came up during the review of #10 (which was intended to fix strongloop/strong-supervisor#73)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants