Thanks for your last reply.
My exact problem is, I want to send some data (json) from client to
everyone who is connected to a conference and I want that this data should
not appear directly to others(like chat), rather it should be saved in the
local storage or cookie of connected clients for some time, so that later
when users will click on a button, I will get that available from the local
storage and show it to clients.
Well, I've done such things before with use of socket.io, but I am not
fully aware of codebase of lib-jitsi-meet and that's why I didn't
understand from where to start.
Will you please help me with this??
Let's keep the discussion on the mailing list.
I'm not the most familiar with Jitsi Meet's signalling, but I will try to
explain to the best of my knowledge.
Jitsi Meet uses XMPP to communicate with others. What I implemented in the
PR I linked to is that I use the chat (which uses a specific element in the
XML of the XMPP signal for the chatroom, just as other data like would be
in other XML elements) to send JSON to the other participants. But instead
of showing the JSON in the chat, we first check if the message is actually
JSON instead of plaintext, and when this is the case a XMPPEvents.
JSON_MESSAGE_RECEIVED is fired instead of
XMPPEvents.MESSAGE_RECEIVED. The chatroom listens for these events, and
fires a JitsiConferenceEvents.ENDPOINT_MESSAGE_RECEIVED whenever a JSON
message is sent via the chatroom. We can than listen for these JSON
messages in Jitsi Meet by adding a callback listener for the
ENDPOINT_MESSAGE_RECEIVED events like I did here . You can than do
whatever you want with the content of the JSON, like storing it in local
 = https://github.com/nikvaessen/jitsi-meet/blob/