@ceejbot,
if FiveBeansClient.prototype.connect() called more than once, a callback for an old socket command may exist in self.handlers even after a new socket is created. In this case, the first command with the new socket will stuck, because its callback will not be called (a callback for the old socket will be called instead).
Suggested fix: #132.
@ceejbot,
if
FiveBeansClient.prototype.connect()called more than once, a callback for an old socket command may exist inself.handlerseven after a new socket is created. In this case, the first command with the new socket will stuck, because its callback will not be called (a callback for the old socket will be called instead).Suggested fix: #132.