-
**Status**: Backlog
**Priority**: P1
**Estimate**: 10 hours
**Size**: L
**Iteration**: Nov 18 - Dec 01
-
Even though they fire twice, onMessage only fires once for the client. Are all additional connections from a single client always closed? If so, why do clientSocket.onOpen and ws.onClient fire twice?
…
-
I set up a Dominatrix dedicated server on a linux machine. The server is externally visible as I tried to connect to it using vanilla Sin (run from a Windows 10 machine) and the game connected properl…
-
## Bug Report
In [LavinMQ](https://lavinmq.com/) it's possible to force close client connections from the broker via the HTTP API. Today I stumbled over a bug where the HTTP request timed out, and …
-
**Is your feature request related to a problem? Please describe.**
It appears that the hyper-util client isn’t currently gracefully shutting down its connection with the server. Specifically, the …
-
**Describe the bug**
In a Socket.IO application, events emitted just before a client disconnects are not properly handled by specific `on(...)` listeners. While the `onAny(...)` listener detects th…
-
**Describe the bug**
A clear and concise description of what the bug is.
Cannot import io from socket.io-client
**To Reproduce**
Use @kellnerd/userscript-bundler to try to bundle `import { io } fr…
-
### Problem:
The hyper client isn't currently capable of shutting down gracefully, and immediately closes its socket after sendings its shutdown to the server. This causes the server to emit a NotC…
-
# Bug report
### Bug description:
I run my client-server application using SSLContext. And during communication I faced with situation when I receive an empty bytes object from the socket on server …
-
# Vulnerability
Currently, the chatroom server uses a **Semi NIO (Non-Blocking IO)** socket system that doesn’t have any form of thread pool but rather creates a thread per connection. Whereas thi…