[ejabberd] pubsub delivery ignores /resource

Peter Saint-Andre stpeter at stpeter.im
Tue Feb 2 18:02:54 MSK 2010

On 2/2/10 7:59 AM, Mickaël Rémond wrote:
> Hello Peter,
> Le 2 févr. 2010 à 15:54, Peter Saint-Andre a écrit :
>> Hi Mickaël!
>> As I understand XEP-0060, if the subscriber JID is user at host/resource
>> then the pubsub service will address notifications to that full JID. If
>> the node is not configured for presence-based delivery then the pubsub
>> service will simple send the notification to the full JID. The
>> subscriber's XMPP server is then responsible for delivering the
>> notification in accordance with RFC 3920 and RFC 3921. That *might* mean
>> the notification ends up being delivered to a different resource.
>> There's no real solution for that at the pubsub service unless the
>> subscription is configured for presence-based delivery. Even then,
>> presence is not fully reliable, as we know. Naturally, if the subscriber
>> doesn't want to receive the notification at another resource then it
>> needs to ensure that the intended resource is always online. That's not
>> always possible, either. These are some of the tradeoffs involved in
>> pubsub. :|
> That's what I guessed as well so I think we are on the same page.
> It seems that we are compliant on this regard, but I will cross check with Christophe when he is back.

Yes, I think ejabberd is compliant here.

> Thank you for your clarification !

You're welcome. Unfortunately, it's not perfect, but then in general
XMPP is not perfect, either. :)


Peter Saint-Andre

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6820 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.jabber.ru/pipermail/ejabberd/attachments/20100202/832b4966/attachment-0001.bin>

More information about the ejabberd mailing list