Hi. I'm using asynchronous SSL socket stuff and I've run into a glitch where SocketController.OnReceive catches and consumes an exception that's thrown by MY code. The result is that I never see the exception. The SSL connection is just silently closed.

An easy fix might be to make OnReceive only catch SocketException and SslException (currently it just catches generic Exception).

A better solution might be to isolate the call to AsyncResult.Notify() (which is in SocketController.ProcessDecryptedBytes) so that it's not contained in any try/catch block.

If this isn't the right forum for bug reports, I appologize. Please point me in the right direction.