Github user mattallenuk commented on the issue:
https://github.com/apache/tinkerpop/pull/889
@jorgebay, I've abstracted out the transport and made some changes to the
DriverRemoteConnection class to handle the authenticator response.
My only concern with the implementation is that there is a potential memory
leak as there is a handler added to the
DriverRemoteConnection._responseHandlers that would never get processed with
sasl authentication. I had played around with adding an addHandler parameter to
DriverRemoteConnection.submit() function which would by default add a handler,
but not sure if this is necessary?
---
