The idea here is provide for a scenario where there is intelligent call routing on the server. Obviously not all servers will support this. <br><br>(Again I don't think that this is necessary for the base jingle xep...)<br>
<br>I would imagine that the client would do a disco to the server to discover if jingle routing is supported. In that case, the client would call the bare jid instead of the full resource and the server would handle this in an intelligent way. This is analogous to sending a message to the bare JID -- it is up to the server to figure out the right resource (or resources) to send this to. It is necessarily more complicated than the simple fire and forget message case since any broadcast results in parallel negotiations (dialogs).
<br><br>Joe<br><br><div><span class="gmail_quote">On 10/12/06, <b class="gmail_sendername">Alexander Gnauck</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Joe Beda wrote:<br>> For all of the steps where Bob (bare) is involved, IQs go between<br>> Alice/home and Bob (bare) and between Bob (bare) and Bob/<resource>. If<br>> Alice/home wants to keep state for each dialog that dialog needs to be
<br>> identified. The extra identification is the responder.<br><br>this is an edge case. Normally we send IQ's to full Jids in XMPP. Who<br>handles the IQ to Bobs Bare jid? I think all current servers will reply<br>with an error message to such an IQ. Or did i get smth wrong here?