-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Auth
-
None
-
2
-
(copied to CRM)
Currently connection handshake looks at whether the connection has a socket, if not it will call the connect call which then will attempt to handshake again. I haven't seen this loop in production but it sometimes happens during development and is very confusing to deal with.
Suggested repair is to make it so that the @socket is only populated when the socket is handshaken and authenticated.