Developers, I got a question about the feature element in service discovery, JEP-0030. In examples 10 and 12, the disco#info query returns some feature elements. I'm trying to find an example that discovers these elements then accesses them in some way, preferrably in IQ sets or gets.
Set question JEP-0030's section 6, Integration with Feature Negotiation, demonstrates how to query an negotiable entry to get an x-data form, then says this "The client would then submit a form in the 'jabber:x:data' namespace containing the required authentication information" So my set question is, what IQ query namespace do I use? Data Forms, JEP-0004, does everything in the jabber:iq:register. Should I use this or define my own namespace (not recommended in this thread http://www.jabber.org/pipermail/jdev/2004-March/018175.html). However, I see that JEP-0045 MUC defines its own query namespace for IQ sets. Using jabber:iq:register might enable me to use clients that support x-data forms. Clients supporting this currently limited. If I define my own namespace, it likely that clients will never support it. Is this only implication? So I'm a bit confused, any help here would be appreciated. Get question Using JEP-0030's section 6 again, lets say that I was able to submit the form and set the var muc-password's value to cleartext. Now another client connects, discovers items, nodes, info and the existence of feature vars. How does it query for the feature var values? How does it determine muc-password is set to cleartext? Could you point me towards an example where a feature var value is queried, I would appreciate that too. Peter Saint-Andre suggested I look through JEP-0045 MUC to find these answers but I was not 100% successful, so I turned here. Thanks, Craig _______________________________________________ jdev mailing list [EMAIL PROTECTED] https://jabberstudio.org/mailman/listinfo/jdev
