Closed woj-tek closed 1 year ago
It is required for SASL2 to reply after binding (bind2) is completed if it takes place and during the binding process we are calling methods that are completing asynchronously, SASL2 sends results using SessionManager as using the results queue from a different thread is not an option.
I also added rudimentary sasl2 unit test and... why it uses session manager directly for failure instead of using results queue?