rethrow in RequestRead

[Steve Douglas]

I've been using Jabber-net for an in-house project, and I've noticed that under some situations an InvalidOperationException ("Cannot call RequestRead while another read is pending.") is getting thrown in RequestRead, in AsyncSocket.

This then gets caught and handled by closing the socket. However, the handler then rethrows the exception. There's no other handler for the exception, therefore the entire thread dies, taking the application with it. Is this correct behaviour? Would it be better to fire an error in order to allow the application to handle the situation a bit more gracefully?