I can not found Broadcast message to a connectionId

[majidbigdeli]

How Sending message to specific user with neffos ?
I can not found Broadcast message to a connectionId

[kataras]

Hello @majidbigdeli,

First of all I am very glad that you are posting questions while this library is still (on the final steps of) work-in-progress!

Secondly, you can already achieve this by connecting the connection to a room with the connection's ID as the room name, this way you can use the nsConn.Room("ID").Emit(...). (the same exactly way that the old Iris' websocket library was able to send To a specific connection but here you have to JoinRoom manually). But let me discuss your alternative below.

It's easy to do something like this, we just have to add a "To" field in the Message and check its value inside the connected namespaces (and rooms) on the Server#Broadcast but to complete a feature like this the "To" connection should be able to see who was the original client sender "From" (because you may want to print its name before the message's body). That was one of my internal questions I had when designing the library, if the library should or not to expose the connection ID (the original client publisher that server-side connection catch and calls its ()Server.Broadcast(Message{})) of the message to the subscribers (to other clients) or not and back then I decided that it's better to not do it for security reasons (the Server#IDGenerator can be used to set connections' IDs based on a custom algorithm, a developer may set this ID to a private database user's row's ID, so we should not expose the sender ID by a "From" field).

At the other hand, the "From" can be solved by the end-developer him/herself by using a custom object and set the Message.Body to the object's serialized form(i.e JSON), and deserialize it on read. An example is also available for encoding/json and even protobufs, check _examples/basic and _examples/protobuf.

As you probably already know from the Go and JavaScript examples,
so far the messages from Server#Broadcast are sent to all connections that are connected to the Message's specific Namespace (and room if Message { Room: "is_not_empty"}) like NSConn,Room#Emit(...) method but to all server's active connections (it does not use loop because it would require a lock to add/remove active connections, instead I used a custom sync.Cond therefore new connections are still able to connect and old can disconnect even while something is broadcasting).

However, we can have an optional Message.To string field among the Namespace and Room fields to decide if an active connection's Emit should be called AND a From field can be sent IF the given To field is not empty and first parameter of the Server#Broadcast is not nil [ OR if set-ed manually (better but this manualy-set of the From field behavior may not be expected by end-developers?)].

Sounds good to you?

[kataras]

It's done @majidbigdeli, just fill the Message.To field.

server.Broadcast(c, Message{ To: "other connecton id", Namespace: "...", Room: "...", Body: ....})

I decided to not expose the from field from the Message at any case, end-developer can send and receive any custom data so they are able to fill if really required, as explained above.

[majidbigdeli]

Hello my friend @kataras .
I read all your commits every day. (Because you are a great programmer)
I work In the Asterisk Manager Interface (AMI) project,
I need to work with the web socket.
I used socket.io before. But after I looked at the neffos project carefully.
I decided to use neffos instead of socket.io . neffos project is very clean project.

Finally, I think you made the right decision.
In my opinion, If someone needs to know who is the original client sender of the message, they can use the custom data.
I agree with this .(can be solved by the end-developer him/herself by using a custom object and set the Message.Body to the object's serialized form(i.e JSON), and deserialize it on read.)

@kataras Thanks for implementing Message.To. ❤️❤️

@kataras Thanks for implementing neffos and neffos.js . ❤️❤️

[kataras]

This post of yours, my friend @majidbigdeli, is one of the most inspirational messages I have ever received for my work, I am really thankful!

Yes, I had a lot of issues working with socket.io at my past career as well. I think a library based on raw websockets is the best option nowdays, note that socket.io has a lot of steps to decide what subprotocol to use for communication(this is the top reason makes that uncompatible with nodejs ws and browser's websockets by-design) and a lot of code which is not even readable for most of the developers over the years. This is one of the main reasons I decided to design and code a decent alternative from zero, hopefully this will be more visible by next months when Iris v11.2 will be released as well ❤️

[lauretagabriel]

Hi @kataras, may I know the estimated date where this project will be fully integrated and stable with the Iris framework? Sorry to sound demanding but really looking forward to use this together with the Iris framework. Thank you!!

[kataras]

Hello @lauretagabriel, I feel you, it's a good question. Expect it until the end of the next week, maybe a bit sooner.

[kataras]

@lauretagabriel @majidbigdeli can I ask you to give some time in order to read and give me feedback about the new neffos wiki Getting Started page, is it understable enough for newcomers and for you? Generally offer some feedback on how to process with it if you want, I want to minimize the README and push a complete guide inside the project's wiki which can be converted to a special book on the future as well. Thank you a lot guys.

[kataras]

@majidbigdeli Thanks a lot!

About JMeter, we can use JMeter with neffos only with the native-only messages because as you understand the JMeter and its plugins are using the websocket API but neffos has its own way to verify a client and to support namespaces, rooms and etc, so we can't use them directly with JMeter because it will stack on the "ack" part of the neffos, they will not pass unless the same neffos websocket client steps are produced. However, if you are an experienced JMeter user you are more fit to do that and share the results with the rest of us.

I'll add a wiki page about native messages, although Iris v11.2 has its own example already, but it looks like this:

Also note that we have a stress-test for neffos specifically, it's located at: https://github.com/kataras/neffos/tree/master/_examples/stress-test

[kataras]

^ https://github.com/kataras/neffos/wiki/Native-messages

[kataras]

Thanks for your nice words and the greek translation too!!! I really appreciate it!!! I am so lucky having you around too! I answered you at the neffos.js project: kataras/neffos.js#2 (comment)