Thanks for pointing out this issue. A few pointers on your proposal:
* On my opinion the hybrid approach is the most practical one. For our
case, we compile from the source each release, but it might seem reasonable
that patch releases maintain both ABI and API compatibility.
* To make s
I think it's only the locator connections that do this. Regular client->server
connections using the handshake code just send the client's current version,
which must not be newer than the server's version.
On 2/1/21, 9:53 AM, "Jacob Barrett" wrote:
Having just spent some time yanking out
One thing that might help somewhat would be to modify the KnownVersion class to
hold both the product version and the client/server protocol version, which
wouldn't have to change if there are no incompatibilities introduced in
client/server comms in a release. That's more in keeping with what
Oh, but I forgot about WAN changes that may have been made to the handshake to
allow different versions in different clusters. Jake might be right about this.
On 2/2/21, 8:31 AM, "Bruce Schuchardt" wrote:
I think it's only the locator connections that do this. Regular
client->server con
Build Update for apache/geode-native
-
Build: #2992
Status: Canceled
Duration: ?
Commit: bddc86b (develop)
Author: Blake Bender
Message: GEODE-8902: parse server destroy reply in gnmsg (#739)
* Parse REPLY from server for DESTROY message
- Reading flags, versi
