[
https://issues.apache.org/jira/browse/GEODE-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McMahon reassigned GEODE-4657:
-----------------------------------
Assignee: (was: Michael Oleske)
Description:
Geode changed the protocol to send a ping interval during client/server
handshake. Update Geode Native to support this change and bump the ordinal
number of Geode Native.
This should _not_ be confused with durableClientTimeout in the system
properties. That value is still expressed in seconds, as far as we can
determine, after speaking with the comms team. This ping interval is a _new_
field tacked on at the beginning of some server responses, and indicates the
timeout interval the server is using for subscription sockets.
If/when we bump our ordinal to use v1.5, there is at least one other observed
breaking change in server responses that _may_ affect us. GEODE-2137 changed
the client membership id field. The ticket states this change was made for
v1.1, which in theory is what we're already using, but we'll need to
investigate and verify whether or not we've already picked this one up.
was:Geode changed the protocol to use ms during the client/server handshake.
Update Geode Native to support this change and bump the ordinal number of Geode
Native.
Summary: Geode Native receives ping-interval field during client/server
handshake (was: Geode Native receives timeouts in ms during client/server
handshake)
> Geode Native receives ping-interval field during client/server handshake
> ------------------------------------------------------------------------
>
> Key: GEODE-4657
> URL: https://issues.apache.org/jira/browse/GEODE-4657
> Project: Geode
> Issue Type: Task
> Components: native client
> Reporter: Addison
> Priority: Major
>
> Geode changed the protocol to send a ping interval during client/server
> handshake. Update Geode Native to support this change and bump the ordinal
> number of Geode Native.
> This should _not_ be confused with durableClientTimeout in the system
> properties. That value is still expressed in seconds, as far as we can
> determine, after speaking with the comms team. This ping interval is a _new_
> field tacked on at the beginning of some server responses, and indicates the
> timeout interval the server is using for subscription sockets.
> If/when we bump our ordinal to use v1.5, there is at least one other observed
> breaking change in server responses that _may_ affect us. GEODE-2137 changed
> the client membership id field. The ticket states this change was made for
> v1.1, which in theory is what we're already using, but we'll need to
> investigate and verify whether or not we've already picked this one up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
