Just curious - what is the use case where sending a stack of bgapi's without listening for the reply is more desirable than looping through the bgapi send/reply sequence for each one? I'm no super programmer but it seems to me that blindly relying on another system to always send stuff in the exact correct order is dangerous and may cause bugs that are difficult to diagnose. Personally I would consider it a programming best practice to wait for the response of the bgapi before sending another one.

I invite other socket programmers to give their input...

-MC

P.S - you may wish to disable the legal notice at the and of your emails when sending to a public list. (We know that some servers tag outgoing messages automatically and if that is your case we understand. Go yell at the I.T. guy! :)

2011/2/24 Mauritz Løvgren <mauritz.lovgren@hotmail.com>
Hi,
 
Are replies for bgapi commands sent back to an inbound socket connection in the same order as the commands were sent?
 
Example: sending 10 bgapi messages from client to freeswitch socket with no delay inbetween.
Will the response for those command messages be sent back by freeswitch in the exact same order as their commands were received, or should one wait for each reply before sending a new bgapi command to be sure one gets a reply for the correct command?
 
If there was an option of providing a UUID (or sequenceId) for the command, it would be easier to match the reply with the request upon receival, but this doesn’t seem to be possible with the current implementation?
 
Regards,
Mauritz Lovgren
Systems Architect
IPLink Inc.