You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[SERVER] Using [email protected] syntax
[SERVER] Server listening on http://127.0.0.1:3000
[CLIENT] Connecting to http://127.0.0.1:3000...
[CLIENT] Connected
[CLIENT] Interrupting...
[CLIENT] State: Connected
[CLIENT] Disconnected
[CLIENT] Connecting to http://127.0.0.1:3000...
[CLIENT] Connected
[SERVER] Expected "of("/user/").use()" {"EIO":"4","transport":"websocket","t":"1605634663","query1":"data1","query2":"data2"}
[CLIENT] Interrupting...
[CLIENT] State: Connected
[CLIENT] Disconnected
[SERVER] Expected "disconnect" ("/user/")
[CLIENT] Connecting to http://127.0.0.1:3000...
[CLIENT] Connected
[CLIENT] Interrupting...
[CLIENT] State: Connected
[CLIENT] Disconnected
Expected behaviour
While the default namespace is no longer detected on [email protected],
I need a way to detect the connection regardless of the namespace to register the existing C++ clients.
Changes introduced in the 3289f7e commit now prevents us
from detecting an "incoming" Client connection, although it does not open a Socket on a namespace,
this is valuable information for specific use cases.
I restored compatibility with the 2.3.0 server by applying this patch after installations :
sed -i "s#\( \)\(new client_1.Client.*\)#\1const client = \2\n client.connect(\"/\");#g" ./node_modules/socket.io/dist/index.js
You want to:
Current behaviour
Upon migration from Socket.IO 2.3.0 to 3.0.1 and related adaptations,
the
socket.io-client-cpp
connections are no longer detected by the server.Only a new
socket("/namespace/")
call in C++ triggers an event.Steps to reproduce (if the current behaviour is a bug)
File
test.js
: test.jsFile
test.cpp
: test.cppCompile
socket.io-client-cpp
andtest
:Run with
[email protected]
and results :Run with
[email protected]
:Results with
[email protected]
:Results with
[email protected]
:Expected behaviour
While the default namespace is no longer detected on
[email protected]
,I need a way to detect the connection regardless of the namespace to register the existing C++ clients.
Changes introduced in the 3289f7e commit now prevents us
from detecting an "incoming" Client connection, although it does not open a
Socket
on a namespace,this is valuable information for specific use cases.
I restored compatibility with the 2.3.0 server by applying this patch after installations :
sed -i "s#\( \)\(new client_1.Client.*\)#\1const client = \2\n client.connect(\"/\");#g" ./node_modules/socket.io/dist/index.js
Per the https://socket.io/docs/v3/namespaces/index.html#Default-namespace documentation,
the default namespace "/" should be at least accessible, even explicitly.
Setup
Other information (e.g. stacktraces, related issues, suggestions how to fix)
For CentOS 7 targets, compatibility for
socket.io-client-cpp
: socketio/socket.io-client-cpp#271The text was updated successfully, but these errors were encountered: