Hi, On Sep 2, 2008, at 5:12 PM, JLIST wrote:
> Thanks Pedro! Although <message /> doesn't get a reply, > I suppose its delivery is still guaranteed by the transport? No, unless you use http://www.xmpp.org/extensions/xep-0079.html and AFAIK no server supports that. So if you need reliability, I would use IQ for now. > I'm thinking, <message /> sounds more efficient than <ip /> <iq />, not <ip />. <ip /> gives me scary thoughts :) > when relatively large amount of data needs to be transferred > because it doesn't require an XMPP level response. it wont be a huge overhead because the IQ response is tiny. And IQ is 2 chars, MESSAGE is 7 :) Best regards, > > >>> A follow up question is, what would be the right element >>> of the protocol to use to send and receive custom data? >>> It'll be very helpful to me if someone can point me to >>> a link or some names that I can search for. > >> You can use two: > >> <message /> or <iq />. > >> the main difference is that <iq /> is a request/response dialog: you >> sen a <iq type="set"> or a <iq type="get"> and get back a <iq > type="result">> or a <iq type="error">. The id attribute of the >> response matches the id of the request. > >> The <message /> is more of a send and forget about it style of >> communication. > > > -- Pedro Melo Blog: http://www.simplicidade.org/notes/ XMPP ID: [EMAIL PROTECTED] Use XMPP! _______________________________________________ JDev mailing list FAQ: http://www.jabber.org/discussion-lists/jdev-faq Forum: http://www.jabberforum.org/forumdisplay.php?f=20 Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [EMAIL PROTECTED] _______________________________________________
