Brandon Potter

Reconnect is tough because you never really know if the TCP connection is really closed until you try and send something and it fails. There’s another related issue to this...

20 should not be anywhere near the number of concurrent connections a TcpListener can accept. Do you have a threadpool restriction? Each client connected will cause a read thread to...

I see no reason this couldn't be added as an optional property. Do you want to submit a PR?

That doesn't seem right. Can you paste the server side code?

Haven't reviewed yet - you guys know if this breaks any existing usage (is this a major or minor rev)?

I suppose we could, what's your unit test scenario where that would be beneficial?

Weird, the library is pretty simple (ha ha) so worst case you can download the repo and add it to your project...

What would be the advantages of 0.0.0.0 vs individual interfaces?

Use `Write(...)` instead of `WriteLine(...)` ?

This is unfortunately a tough problem to solve for TCP all around. If you're not sending traffic, you can't clearly determine if a client has disconnected. Best solution I've found...