[Standards-JIG] JEP 60: Resource Based Subscription problem

Kevin Smith kevin at kismith.co.uk
Mon May 23 17:21:00 UTC 2005

Hash: SHA1

Advanced appologies if this reply efficiently illustrates my complete 
lack of understanding of the topic. I should have referred to the jep 
first and haven't.

On 23 May 2005, at 17:39, Peter Saint-Andre wrote:
>> Have the message routing rules for PubSub been explicitly defined
>> anywhere?
> It seems not, so we need to define them.
> As a first pass, I think a pubsub service MUST send to the subscribed
> JID and not make any assumptions about sending to some other JID, even
> what looks like a "bare JID" (node at domain) if the subscribed JID looks
> like a "full JID" (node at domain/resource). Naturally other handling 
> rules
> make apply given the subscription options (see below).

Does this apply in reverse? That a subscription from a node at domain 
shouldn't result in a delivery to an online node at domain/resource? If 
you cannot make assumptions one way, I assume that means you cannot 
make assumptions in reverse. The reason I ask is I'm confused as to 
what would happen, as online-ness is related to a resource, would a 
user ever receive a notification if they subscribe with their bare jid, 
and offline pushes aren't enabled?

>> Should messages be stored offline if there isn't an exact match?
> Pubsub services don't have a concept of offline storage, they simply
> have a concept of notification push (or not). Whether to push to an
> offline resource is handled by the pubsub#show-values subscription
> option

Please disregard if I'm being dense.

- --
Kevin Smith
Psi Jabber client maintainer (http://psi.affinix.com/)
TaeKwon-Do Club Captain (outgoing) University of Exeter
Postgraduate Research Student, Computer Science, University Of Exeter
Version: GnuPG v1.2.4 (Darwin)


More information about the Standards mailing list