I've been looking at XMPP uri processing and the different query types [1] and I'm curious if anyone has defined more GET/POST/etc. semantics for thees URI values?
I've been integrating XMPP URI support into Restlet [2] and I'm struggling with the right processing model. As Restlet has a uniform processing model, the method is less of a constraint. For example, I could "POST" or "GET" on: xmpp:[email protected]/desktop?message;body=hello+world without an entity body and have the semantics be the same (i.e. send a message). Neither would return an entity body because of the asynchronous nature of XMPP. As "POST" is more usually associated with "sending data", it seems like that is more appropriate. I have enabled both but I'm curious as to the intended use. [1] http://xmpp.org/registrar/querytypes.html [2] http://www.restlet.org -- --Alex Milowski "The excellence of grammar as a guide is proportional to the paucity of the inflexions, i.e. to the degree of analysis effected by the language considered." Bertrand Russell in a footnote of Principles of Mathematics _______________________________________________ JDev mailing list Forum: http://www.jabberforum.org/forumdisplay.php?f=20 Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
