Stephen Pendleton wrote: > Now my question/comment is, is this the best way to do this? What is the > advantange of sending a jabber:x:data form? Will there be implementations > that require jabber:x:data data to be sent back? The only reason I ask this > is because it seems to me it is pretty much the same as a simple "roster > subscription request" that would require only a simple yes/no response sent > back.
The advantage of using x-data here is so that x-data compliant clients do not need to implement yet another namespace for just a simple form. X-Data is perfectly suited for this type of operation. It's also not JUST a yes/no since the approver probably wants to see who the requestor is, and what NODE they are trying to subscribe to. Thus, there is a some basic information that needs to be displayed to the approver. In general, it's just not necessary to force clients to implement yet another bit-o-protocol, when we already have something that can be used. Re-use of protocol is a GOOD thing :) pgm. _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
