On Friday 09 November 2007 23:54:03 Lindsay Oproman wrote:
> Hello,
>
> I have a question about subscription authorization that I was hoping
> someone on this list might be able to help me with. I didn't see
> anything in the documentation that answers my question. This may be
> because I am new to XMPP and do not fully understand how resources are
> treated by the server.
>
> Essentially, what I'm trying to do is have notifications sent to *all*
> FULL JIDs of a subscriber upon publication. For example, [EMAIL PROTECTED]
> subscribes to a topic. Something is then published to that topic. I
> want a notification to go to both [EMAIL PROTECTED]/resourceA and
> [EMAIL PROTECTED]/resourceB... not just the primary entity (whatever that
> may be).
>
> So, I figure one way to do this is to have [EMAIL PROTECTED]/resourceA and
> [EMAIL PROTECTED]/resourceB both explicitly subscribe to the topic (using
> their full JID). However, this is where my question regarding
> authorization comes in. If [EMAIL PROTECTED] is white listed, will
> [EMAIL PROTECTED]/resourceA and [EMAIL PROTECTED]/resourceB be granted access
> all the same? Alternatively, if the topic is using authorization
> access mode, if authorization is granted to [EMAIL PROTECTED], will
> individual authorization still need to be granted to both
> [EMAIL PROTECTED]/resourceA and [EMAIL PROTECTED]/resourceB?
In the 6.1.1 it is explicitly mentioned that you can subscribe either an 
individual resource or a bare jid.

You see - pubsub component generally do not knows what resources are online at 
the moment - so it just can't guess where to send updates. If you are 
subscribed by the bare jid - it will send update to it and _your_ server will 
take care of delivery.

Most servers deliver <message/>s only to one resource - so most often it will 
be the case. However the RFC leaves it to the server's discretion - i.e. 
server MAY distribute it to one or all resources.
So I can make a conclusion that deliver of updates to the bare jid is
1) server-specific
2) question of _your_ server configuration

>
> Thanks!
>
> Lindsay


-- 
Respectfully
Alexey Nezhdanov

Reply via email to