Kk, makes sense then if they remain constant. I can't make the nodes allow open subscription since I do want the user to be able to turn on and off the automatic subscription via the UI. What I am working on is a pubsub implementation of location information (latitude, longitude), and I do want the user to have the option of not allowing everyone to subscribe to this data.
BTW, so far the pubsub implementation is working well! -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Peter Millard Sent: Friday, March 07, 2003 4:09 PM To: [EMAIL PROTECTED] Subject: Re: [JDEV] PubSub Subscription Requests Stephen Pendleton wrote: > Understood. Makes sense. The reason is that in my client I am attempting to > automatically allow people to subscribe to my node, and I am attempting to > find a robust way of parsing this node. Why not just configure the node to allow open subscription? Does your server not allow this?? > I am assuming that the var attributes in the "field" tag are not > nescessarily always going to be "node" and "subscriber_jid". Yeah, the should be. The Jabber Registrar should "register" those in conjunction with the FORM_TYPE of http://jabber.org/protocol/pubsub. This allows you to build this functionality into your client and have those field variable names enver change. I see this is not explicitly spelled out in section 11 of the JEP as it should be. pgm. _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
