The JEP is still under heavy development. As the Jingle JEP settles down we'll move libjingle to follow it.<br><br>A lot of the core ideas are the same, but the JEP is moving in a direction that is better factored and more generic.
<br><br>Joe<br><br><div><span class="gmail_quote">On 3/31/06, <b class="gmail_sendername">Stephen Pendleton</b> <<a href="mailto:spendleton@movsoftware.com">spendleton@movsoftware.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;">
I've been doing some implementation work using libjingle and referencing<br>JEP-0166 and I have noticed that libjingle version 0.2.1 and the JEP-0166 do<br>not seem to match up. For example in JEP-0166 Example 1 displays an example
<br>initiation stanza:<br><br><iq to='<a href="http://juliet@capulet.com/balcony">juliet@capulet.com/balcony</a>' from='<a href="http://romeo@montague.net/orchard">romeo@montague.net/orchard</a>'<br>id='jingle1' type='set'>
<br> <jingle xmlns='<a href="http://jabber.org/protocol/jingle">http://jabber.org/protocol/jingle</a>'<br> action='session-initiate'<br> initiator='<a href="http://romeo@montague.net/orchard">romeo@montague.net/orchard
</a>'<br> sid='a73sjjvkla37jfea'><br> <description ...><br> <transport ...><br> </jingle><br></iq><br><br>but Libjingle outputs:<br><cli:iq to="<a href="http://foo@gmail.com/Talk.v860770CBCA">
foo@gmail.com/Talk.v860770CBCA</a>" type="set"<br>xmlns:cli="jabber:client"><br><session xmlns="<a href="http://www.google.com/session">http://www.google.com/session</a>" type="initiate"
<br>id="3245625544" initiator="<a href="http://foo@gmail.com/imov">foo@gmail.com/imov</a>"><description<br>xmlns="<a href="http://www.google.com/session/phone">http://www.google.com/session/phone
</a>"><br><payload-type xmlns="<a href="http://www.google.com/session/phone">http://www.google.com/session/phone</a>" id="102"<br>name="iLBC"/><br></description><br></session>
<br></cli:iq><br><br>Should I just attribute this to the fact that both the JEP and libjingle are<br>under heavy development? Or am I missing something major? I am assuming that<br>libjingle and the JEP's will converge at some point. I did see that
<br>libjingle 0.3.0 is out so perhaps that will fix some of these issues.<br><br>Thanks,<br>Stephen<br><br><br></blockquote></div><br>