Pushkar Niranjan Kulkarni

@stealthanthrax HTTPStatusCode is bridged from `Kitura-net` by default, and from `Kitura-NIO` (in the NIO mode). If we decide to go ahead, the changes should go into both of these packages.

Fix proposed via https://github.com/fenderglass/Flye/pull/670

Nice discussion. My two cents: I'd be little careful before calling this out as a _bug_ in either Temurin packages for Debian or the latter's own OpenJDK packages installed through...

Thanks for reviewing @weissi ! I've addressed your comments.

Sorry, I had posted something related to another issue here. Deleted it. Please ignore the notifications, if any!

@bridger I wasn't able to repro what you said with 10-12 tabs. So, I wrote a [JS client](https://gist.github.com/pushkarnk/b63275f98acfe86d6251074c54e6dc9c) that makes N connections to the [test WebSocket server](https://github.com/IBM-Swift/Kitura-WebSocket-NIO/tree/master/Sources/TestWebSocketService), sends two messages...

I also found a new Kitura-NIO bug testing with the JS client: https://github.com/IBM-Swift/Kitura-NIO/pull/215

Ported IBM-Swift/Kitura-WebSocket#48 through #40

I think I have found the reason for the WebSocket connection not receiving all the `disconnected` notifications. It is a bug in `Kitura-NIO`. Here's the possible fix: https://github.com/IBM-Swift/Kitura-NIO/pull/217 I ran...

Thanks @weissi and @bridger for the investigation - Yes, we should implement those callbacks. I'll take that up (Sorry for the late response, I was away yesterday).