[Jingle] XEP-0176 - putting many candidates in initiate/accept

Peter Saint-Andre stpeter at stpeter.im
Wed Apr 8 17:20:33 CDT 2009

On 4/8/09 4:16 PM, Justin Karneges wrote:
> On Wednesday 08 April 2009 15:04:30 Peter Saint-Andre wrote:
>> On 4/7/09 6:34 PM, Justin Karneges wrote:
>>> Peter says this was to help simplify the state machine.
>>> However, transport-info is still in the XEP and expected to be supported,
>>> so I don't see how this resulted in any simplification.  I just wanted to
>>> point out that if anyone is planning to write a client that doesn't
>>> understand transport-info (/me looks at whoever suggested this change),
>>> compatibility will be lost.
>> Clients need to support transport-info. If they don't, we'll file bug
>> reports. :)
> Good.  But, then I don't fully understand the rationale for putting candidates 
> in initiate/accept and therefore having two ways to do the same thing.

Save some packets. Let's say that up front you have 5 candidates. Why
send each one in a separate IQ when you can send them all in the session
initiation request?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6751 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/jingle/attachments/20090408/5a8f5f25/attachment.bin 

More information about the Jingle mailing list