3 ms·

Depends on the differences, but generally - no, of course, not.

• kjgkjhfkjf 7y ago
  It'd be useful if you mentioned this in your caveats list, since version skew is a common gotcha that some serialization technologies (e.g. protobuf) are designed explicitly to address.
  • apankrat 7y ago
    OK, will do. I assumed it was obvious that schemas on both ends must match.
    • quietbritishjim 7y ago
      I would assume it's obvious that schemas on the two ends don't need to match because solving that problem is usually a basic requirement of a serialisation library. Of course they need to be compatible in some way though e.g. in protobuf, don't reuse old field numbers.
      • apankrat 7y ago
        Depends on the project. Lots of cases when there's no need for schema versioning. For example, when two processes need to talk to each other and they both run from the same binary or share the exact same datamodel. Even if they aren't run from the same binary, it's often much simpler to just require both sides to use the same protocol revision.