Reconnect should create new handler instances #317
Labels
type: enhancement
A general enhancement
Milestone
Comments
mp911de
added a commit
that referenced
this issue
Sep 3, 2016
Refactoring of CommandHandler and connection handling. Lettuce now uses the Endpoint concept to represent communication with a server. Endpoints may be in a connected or disconnected state and are used by the stateful connection. Channel handlers are no longer reused but registered per channel pipeline. Each CommandHandler has its own queue instance to keep track of alive command processing. Command buffering (disconnected endpoint) is held on endpoint level. The stateful connection is no longer required to be a command handler but can be notified from endpoints (see PubSubEndpoint).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reconnection retains handler instances. This leads sometimes to issues like #315 that two channels are bound to one
CommandHandler. Reconnection should create a new set of instances and transfer the state from the old handler to the new one. Ideally, the state is held outside the handler.The text was updated successfully, but these errors were encountered: