[Standards-JIG] JEP 60: Resource Based Subscription problem
kevin at kismith.co.uk
Mon May 23 17:51:22 UTC 2005
-----BEGIN PGP SIGNED MESSAGE-----
On 23 May 2005, at 18:39, Peter Saint-Andre wrote:
> On Mon, May 23, 2005 at 06:21:00PM +0100, Kevin Smith wrote:
>> On 23 May 2005, at 17:39, Peter Saint-Andre wrote:
>>>> Have the message routing rules for PubSub been explicitly defined
>>> 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,
>>> what looks like a "bare JID" (node at domain) if the subscribed JID
>>> like a "full JID" (node at domain/resource). Naturally other handling
>>> 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
>> and offline pushes aren't enabled?
> Notification != delivery.
I get this but it wasn't quite my query;
A service may do presence-based delivery of events. If it's not
possible to map from node at domain to node at domain/resource, how does the
service check that the user is online for delivery in such a situation?
I realise that if the service /does/ determine that the user is online,
the XMPP server will correctly route it according to the RFC. It's the
service level that I'm concerned about.
As I say, I could be being dense in needing this spelled out to me, so
this isn't an aggressive YOUR JEP SUCKS OMGWTFLOL mail, but it's not
clear to me.
Psi Jabber client maintainer (http://psi.affinix.com/)
TaeKwon-Do Club Captain (outgoing) University of Exeter
Postgraduate Research Student, Computer Science, University Of Exeter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
-----END PGP SIGNATURE-----
More information about the Standards