|Subject:||Re: [osip-dev] re-ordering of outgoing requests ?|
|Date:||Tue, 10 Feb 2015 13:04:41 +0100|
The "send" events are non-blocking.
This means that a message could be sent in second retry for first transaction and in first try for second transaction.
This is happening in many use-case because the first transaction usually setup the connection and doesn't wait. When second comes, the network connection is ready. (That's the most common example)
Otherwise, it is possible that exosip_execute is processing non-invite events in the non-invite fifo before processing invite events in the the invite fifo... Thus, if you ask for those actions at the same time, you end up with info being sent first.
Those "fifo" are separated.
I'm on holiday... So this is a blind answer ;) with no code checking!
It might also be good to avoid sending 2 transaction in the same dialog at the same time...
asynchronously, yes – but in the same order (FIFO) as the app called the appropriate eXosip_..._send function ?
The request are sent asynchronously.
No doubt what you describe will happen!
Le 10 févr. 2015 01:23, "FEICHTER Christoph" <address@hidden> a écrit :
my question is about outgoing requests.
I send a re-INVITE and immediately after that an INFO request.
I see these 2 requests in the other order on wireshark, than I sent them using eXosuip –
first the INFO, then re re-INVITE.
is it possible that eXosip changes the order of subsequently sent requests ?
|[Prev in Thread]||Current Thread||[Next in Thread]|