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

Message compatibility #64

Open
ndantam opened this issue Nov 2, 2013 · 0 comments
Open

Message compatibility #64

ndantam opened this issue Nov 2, 2013 · 0 comments
Labels

Comments

@ndantam
Copy link
Member

ndantam commented Nov 2, 2013

Looking at the latest release, a field was added to the middle of hubo_state_t. This will break binary compatibility with applications compiled against the old header. The normal way to handle binary compatibility is with a library version number. However, since hubo-ach and its clients are separate processes, library versioning (alone) won't work for this.

What is a good way to handle message compatibility?
Some options:

  • Punt. Users must recompile.
  • Switch to a full-blow serialization library, e.g., protobuf.
  • Add version number to messages
  • Only append fields. Clients must be able to accept messages larger than what they were expecting, and must ignore the updated end of the message.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant