However, when the "Cancel" button is clicked, some clients do not return the <thread> element. In the JEP in Section 3.2, it states, "For <message/> packets, copy the <thread/> into the reply, and make sure that the jabber:x:data packet is a child of the <message/>."
To reiterate, can the JEP authors clarify that the <thread> element should be returned in all use cases, including the "cancel" case?
In building multiple step processes using x:data, it is imperative that the application can maintain the context of the user's input across several <message> x:data packets. In addition, the "cancel" case must be contextual also, as the application will need to make a decision (or prompt the user) on what to do with the data already gathered.
For more advancd use of x:data, this context must be available to ensure data integrity and process logic.
paul
_______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
