[jdev] PubSub Subscription Question
chris.mullins at coversant.net
Sat Apr 9 13:28:14 CDT 2005
JEP 60 (PubSub) lays out the ability for an entity to subscribe to a
Node (Section 8.1.5)
Node Affiliations however are defined for a particular JID regardless of
the JID's form (server, user at server, user at server/resource).
Suppose that user at jabber.org has an affiliation of "Outcast" to Node 1.
The way the spec is written user at jabber.org/test would be allowed to
subscribe to the node.
The converse case is also true - if user at jabber.org/test has an
affiliation of Outcast, user at jabber.org would be allowed to subscribe to
Other than removing the "a jid in the form of user at server/resoruce can
subscribe to a node" feature (which I think would be a positive step
forward), there aren't too many clean soutions.
We could define an affiliation heirarchy:
1 - An affiliation at the server level (server) is tested first, so that
affiliations can be defined based soely on domain. If such an
affiliation is found, no further affiliation checks are made.
2 - An affiliation at the user at server level is tested next, so that
affiliations can be defined at the user level. If such an affiliation is
found, no further affiliation checks are made.
3 - An affiliation at the user at server/resource level is tested last.
This would break existing implementations, so is obviously not a great
How have the other implementations solved this problem?
More information about the JDev