wonder if this will affect the WAN - do we want to keep sending
the current product version with the WAN, or use the client protocol version?
-Dan
From: Bruce Schuchardt
Sent: Tuesday, February 23, 2021 9:38 AM
To: dev@ge
or use the client protocol version?
-Dan
From: Bruce Schuchardt
Sent: Tuesday, February 23, 2021 9:38 AM
To: dev@geode.apache.org
Subject: [DISCUSS] client/server communications and versioning
I’m considering a change in client/server communications th
From: Bruce Schuchardt
Sent: Tuesday, February 23, 2021 9:38 AM
To: dev@geode.apache.org
Subject: [DISCUSS] client/server communications and versioning
I’m considering a change in client/server communications that I would like
feedback on.
We
the WAN - do we want to keep sending the
current product version with the WAN, or use the client protocol version?
-Dan
From: Bruce Schuchardt
Sent: Tuesday, February 23, 2021 9:38 AM
To: dev@geode.apache.org
Subject: [DISCUSS] client/server communications and
Sounds reasonable. We increment the serialization version every minor release
"just in case" anything has changed in the server-to-server protocol, but
client-to-server should change a lot less frequently, as you pointed out.
Now that Geode is maintaining support branches with longer life, rath
+Geode+clients+to+connect+to+older+Geode+servers
BR,
Alberto G.
From: Bruce Schuchardt
Sent: Tuesday, February 23, 2021 6:38 PM
To: dev@geode.apache.org
Subject: [DISCUSS] client/server communications and versioning
I’m considering a change in client/server
I’m considering a change in client/server communications that I would like
feedback on.
We haven’t changed on-wire client/server communications since v1.8 yet we tie
these communications to the current version. The support/1.14 branch
identifies clients as needing v1.14 for serialization/deser
