Hello,
I'm reviewing different message passing solutions before starting a new project and would like to know if the following case would make sense with ejabberd.
We would have one master user and one thousand thin users:
- the master user should be able to *broadcast* the same message to all thin users
- and then all thin clients reply (all in 1-second time window) to the master with a message: *gather*.
- thin clients do not need to exchange messages with other thin clients
That would be one "chat" room, there would be several chat rooms with this scheme but different master and thin users.
My questions are the following:
- Is this pattern fit XMPP / ejabberd features?
- Can 1 ejabberd server broadcast one message to 1000 clients in less than 1 sec? Of course, it depends a lot on the server class, network ... but what is your experience?
- If a cluster of ejabberd servers is used can a chat room be splitted over several servers?
- When a thin user sends a message and cannot be delivered, does the thin user receive a notification?
Thanks,
Cosmo
Cosmo wrote: - Is this
- Is this pattern fit XMPP / ejabberd features?
Yes.
- Can 1 ejabberd server broadcast one message to 1000 clients in less than 1 sec? Of course, it depends a lot on the server class, network ... but what is your experience?
If there's only one room with 1000 occupants, probably yes with any basic machine. If it's several rooms with such activity every few seconds... then it will require a good machine.
- If a cluster of ejabberd servers is used can a chat room be splitted over several servers?
No. From what I remember, each room lives only in the node where it's created. Any user connected to any of the nodes can join that room. And different rooms can live in different nodes.
- When a thin user sends a message and cannot be delivered, does the thin user receive a notification?
It depends on the cause of the problem, but in general there isn't guarantee.