[reSIProcate] Concurrent info transactions

[Byron Campen]

	That restriction ensures that the other end will get the INFO  
requests in the right order; if you send another before the response  
to the first comes in, they can arrive in the opposite order at the  
other end.

	Are you sure you want this still?

Best regards,
Byron Campen

> Hi,
> Current InviteSession::info implementation doesn't allow concurrent  
> info transactions, but there is nothing wrong in having more then  
> one concurrent in-dialog transaction as long as it is not INVITE  
> transactions. Can we remove this restriction at least for info  
> transactions?
>
> Thanks,
> Boris
>
>
>       
> __________________________________________________________________
> Instant Messaging, free SMS, sharing photos and more... Try the new  
> Yahoo! Canada Messenger at http://ca.beta.messenger.yahoo.com/
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2423 bytes
Desc: not available
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20080724/cb180442/attachment.bin>