You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Connection activation right now reissues state commands required for restoring the connection state. Commands are written as regular commands which can interfere with request queue sizes. Also, subsequent activations can cause maintenance commands to pile up - i.e. activations get interrupted/disconnected and maintenance commands are dequeued into the disconnected buffer and replayed.
The text was updated successfully, but these errors were encountered:
Connections are now initialized with a ConnectionInitializer that performs the Handshake and issues initialization commands after the handshake. The ConnectionState keeps track of the desired state and applies it on connect and reconnect. This change removes the need to track the state of each connection flag in each connection implementation and moves all flags into a single state object.
The initialization/handshake future is now also provided by RedisHandshakeHandler instead of living in various initializer types.
The handshake for SSL and plaintext connections became simpler and easier to find.
Centralizing the handshake is a pre-requisite for protocol version negotiation.
Connection activation right now reissues state commands required for restoring the connection state. Commands are written as regular commands which can interfere with request queue sizes. Also, subsequent activations can cause maintenance commands to pile up - i.e. activations get interrupted/disconnected and maintenance commands are dequeued into the disconnected buffer and replayed.
The text was updated successfully, but these errors were encountered: