my first attempt is based on code that was already present in ts_jabber_common.erl,
just added the way to configure it in js_config_jabber.erl.
provide three messages types:
<jabber type='pubsub:create' ack = "local" node = "relativePath|absolutePath"/>
<jabber type='pubsub:subscribe' ack = "local" node = "relativePath|absolutePath" dest = "random|online|offline|User"/>
<jabber type='pubsub:publish' ack = "noack" node = "relativePath|absolutePath"/>
But now I'm having problems building a concrete scenario with those primitives.
Basically, I need a set of publishers and a set of subscribers, easily done with two different session.
The problem then comes, how do I know what UsersID are "publishers", so subscriber knows where to
subscribe? (publishers put items in their own hierarchy).
I think It can be done by having a global process keeping track of active publishers, and subscribers choosing one from
But I'm wondering if I'm thinking the whole problem in the wrong way, and there are better approaches to generate pubsub load?.
Also, in the future it could be interesting to know the end-to-end delay, between the instant when the publisher put a new item, and when all
subscribers receive the notification. But currently we aren't measuring this for any of the other cases neither (presence, muc, one to one messages).