Katy

And btw yes, it is tricky because all the 3rd party libraries expect to manage the sockets themselves, and all of the protocol handling is in private methods. That is...

Actually last night i figured out (in my head) how to do option 3 and also use websocket-sharp. Im away for a couple of days now but the basic idea...

Okay, I will whip up some kind of draft code and we can move things around from there.

The connection will always be self-initiated btw, IrcConnection will call some connect method on the IrcSession-implementer. If the session gets disconnected, IrcConnection will receive an OnDisconnect-style event and just re-connect.

Okay I've got it all working after 10 hours of marathon coding, including WebSockets as an example secondary protocol using websocket-sharp. I'm just gonna juggle some things around and then...

Re the linked comment, this is threading code, not socket-specific code afaics. In any case, the WebSocket implementation i have at the moment doesn't conflict with this. It uses the...

The whole threading code has been pulled apart in pr 37 where socket handling is abstracted to allow multiple transports. Thread.Abort is removed from some of the code there by...

Stream reads with StreamReader are blocking and do not accept a timeout. I went through this problem myself trying to find a solution on the other pr. You can call...

Also, if you call await readlineasync, you are creating an additional thread negating the purpose of the existing read thread, and if you are doing it in a loop you...

I'll fix it in this branch. I've already merged a few code paths where threads are unnecessarily closing things that were already half-centralized in Disconnect(). It's a nightmare to abstract.