On 2013-05-10 05:04, Peter Saint-Andre wrote:
On 5/8/13 2:05 AM, Krishna Chaitanya (kchaitan) wrote:
Hi,
I would like to submit an enhancement to XEP-0060 specification to
provide a mechanism for the node owner to subscribe a client /*with
subscription options*/. As per section 8.2.2 (Modify Subscriptions) of
the specification, the node owner can change the subscription state of a
client to 'subscribed' using the below stanza.
Hi Krishna,
It does seem to be an oversight that a plain user can subscribe,
configure subscription options, or subscribe-with-options, but an owner
can only subscribe a plain user. The solution you propose appears
reasonable to me.
The reason that changing the subscription status is a different
protocol, is that allows for batch processing. We don't really like that
so much these days, and in retrospect we probably should just have used
the existing protocol for subscribe/unsubscribe with proper
authorization checking. Also, this protocol doesn't support multiple
subscriptions (with SubIDs) at all.
I would like to suggest using the existing protocol in section 6.3
(Configure Subscription Options) for changing a user's subscription
options and implement proper authorization checking on the sender JID
against the affiliations for that particular node.
--
ralphm
