We are currently working on the XEP. Is there some comments to make on
this new structure ?
<iq type='set'
from='[email protected]'
id='sub123'>
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
<publish node='urn:xmpp:pubsub:subscription'>
<item server="pubsub.etu.univ-nantes.fr" node="mlp"
id="2SjNoqvGNLLXv+6w+4+mbEZ">
<title>My Little Pony - Fan Club</title>
</item>
<item>
...
</item>
</publish>
</pubsub>
</iq>
The server attribute is REQUIRED
The node attribute is REQUIRED
The node id is RECOMMENDED
The node title id OPTIONAL
An entity will have to add urn:xmpp:pubsub:subscription+notify to it's
Entity Capabilities list to receive all modifications made on this PEP
node.
The Pubsub URI proposed XEP
(http://xmpp.org/extensions/inbox/pubsub-uri.html) is also quite
interesting for us to simplify the access path to the listed nodes. Do
you have any comments to make on this XEP ?
Timothée Jaussoin
2013/2/12 Kim Alvefur <[email protected]>:
> On 2013-02-12 10:16, Steffen Larsen wrote:
>> yes scaling and performance issues in 2.x is quite known… And I don't even
>> think that Ejabberd 3.0 will be open sourced. You should take a look at
>> mongooseIM, that is an erlang solutions open source fork.
>
> Or use Prosody!
>
> Best regards,
> Kim "Zash" Alvefur
> Prosody Marketing Department
>
>
