Enhancement #457
Remove Notification.version?
Status: | Resolved | Start date: | 07/29/2011 | |
---|---|---|---|---|
Priority: | Low | Due date: | ||
Assignee: | J. Moringen | % Done: | 100% | |
Category: | Protocol | |||
Target version: | 0.4 |
Description
The field
Notification.version
is currently not processed in any implementation (I think). I propose removing it:
- Saves five bytes
- We have/want build-time checks now
- We cannot handle incompatible changes at runtime anyway
- Also, we can detect incompatible versions differently:
We can use a required field likeNotification.sequence_number
and set the field number to100 + ${WIRE_PROTOCOL_VERSION}$
This would make protocol buffer unpacking fail for incompatible wire protocol versions
Associated revisions
Removed Notification.version field in protocol/RSBProtocol/Protocol.proto
refs #457
refs #457
- protocol/RSBProtocol/Protocol.proto: removed unused
Notification.version field; bumped filed number of
Notification.sequence_number to 100 to make this usable for
detection of wire-format incompatibilities
Added field number from wire format in protocol/
fixes #457
fixes #457
- protocol/CMakeLists.txt: generate field number of
Notification.sequence_number based wire format version number;
configure protocol/RSBProtocol/Protocol.proto.in with this field
number - protocol/RSBProtocol/Protocol.proto.in: renamed
protocol/RSBProtocol/Protocol.proto ->
protocol/RSBProtocol/Protocol.proto.in
History
#1 Updated by S. Wrede over 12 years ago
Sounds good to me. I propose to do this now as we did change the protocol for 0.4 anyway...
#2 Updated by J. Moringen over 12 years ago
- Status changed from Feedback to In Progress
- Assignee changed from J. Wienke to J. Moringen
- Target version set to 0.4
#3 Updated by J. Moringen over 12 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset r2171.