[OpenSIPS-Users] async() and config actions call stack

[Vitalii Aleksandrov]

Hi opensips team and community,

     Want to share one headache I have which might be converted into a 
feature request. It's about async() implementation. I use it, like 
probably many of us, for db operations and http requests and it's so 
complicated to insert an async() call so some already written and tested 
config. The requirement to set a "resume_route" and continue request 
processing in it forces to break a script into "before async" and "after 
async" parts. If you have only one async() call during request 
processing it's more or less manageable and when it comes to many 
async() operations it becomes a nightmare.

     I'm dreaming about the way to just "return" from a "resume_route" 
and continue script execution from the instruction next to the place 
were async() was called. Frankly speaking I didn't check how it's 
implemented and config execution part of opensips is a blackbox for me. 
So I assume there might be some architectural reasons and obstacles 
which don't allow to make it this way.

     Haven't found anything related in 3.0 roadmap. I'm sure this would 
be very beneficial for all opensips users.

Feedback and comments are appreciated.