[jdev] Communicate between two client instances of the same ID

[JLIST]

Thanks Pedro! Although <message /> doesn't get a reply,
I suppose its delivery is still guaranteed by the transport?
I'm thinking, <message /> sounds more efficient than <ip />
when relatively large amount of data needs to be transferred
because it doesn't require an XMPP level response.

>> 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.