< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] Concurrent info transactions


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@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel

Attachment: smime.p7s
Description: S/MIME cryptographic signature