[
https://issues.apache.org/jira/browse/CASSANDRA-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984257#action_12984257
]
Gary Dusbabek commented on CASSANDRA-2012:
------------------------------------------
This is like the approach you advocated in CASSANDRA-1970 (first message is an
unalterable way to identify the communications that follow).
If CASSANDRA-1015 ends up using a pre-existing framework for serialization, it
would be good if protocol version could be part of the session and not each
individual message (simplifies the logic of collecting it). The reasoning, for
avro at least, is that this is also the time when when the protocol is sent and
knowing the version is the only way to know if what comes next is an old-school
message or something radically different.
OTOH, if 1015 just extends the current ICompactSerializers to handle
versioning, we wouldn't need this ticket, but I think it still makes sense. It
enables a certain kind of flexibility wrt to interpreting internode messages.
> handshake protocol version during connection setup.
> ---------------------------------------------------
>
> Key: CASSANDRA-2012
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2012
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Gary Dusbabek
> Assignee: Gary Dusbabek
> Fix For: 0.7.1
>
> Attachments: 0002-node-sends-version-message-at-startup.patch
>
>
> Really this is for 0.7.2.
> CASSANDRA-2011 created verb padding so that 0.7.1 nodes don't blow up as
> 0.7.2 nodes are brought up and start exchanging their version information.
> This is related to CASSANDRA-1015.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
