-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emit with multiple parameters #246
Comments
Do you use a special parser for this on the server side? |
No. We don't use any parser beyond the default behavior of the nodejs package server-side.
As seen here the emit function takes an unbound number of arguments. This behavior is handled server side as per this example |
rust-socketio/socketio/src/socket.rs Lines 105 to 109 in 4ac27c7
socket .emit("foo", "bar1\",\"bar2\", \"bar3") , you can have a try.
|
@SSebo is there currently a better way to do this using "binary data/attachments"? I know your todo list is probably long, but a proper interface for encoding multiple message parameters would be a great feature :) |
@1c3t3a @nshaaban-cPacket they are the owners of this repo, I forward your message to them :) |
#249 I made a PR @david-sailplan @syshriki9 You can have a try. |
Wow that was fast!, Thanks @SSebo. As David mentioned, it seems to work. |
also. that…… |
This issue is mostly done, likely able to close |
The Client.emit and Client.emit_with_ack only seem to support a single data parameter
This causes issues for servers who are expecting multiple parameters for the data for these events
rust.rs
example_socketio_server.js
no mater what is placed in data, it will place all data under the "userId" and no way to populate the body parameter.
Is there a workaround that could fix this?
The text was updated successfully, but these errors were encountered: