Liviu,<div>This is a good idea. What happens to the child process as it's waiting for a lock to be released? Are there any protections against locks lasting indefinitely? </div><div><br></div><div>Thanks,</div><div>Brett</div>
<div><br><br><div class="gmail_quote">On Wed, Nov 28, 2012 at 9:02 AM, Liviu Chircu <span dir="ltr"><<a href="mailto:liviu@opensips.org" target="_blank">liviu@opensips.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The cfgutils module now provides the possibility of defining atomic<br>
test-and-set operations in the OpenSIPS script.<br>
Such need is a result of complex mixing in script of various<br>
functionality / functions from different modules. Like testing<br>
is done based on ratelimit module and the setting is done in<br>
dialog module.<br>
<br>
Modules do provide internal locking and synchronization for their<br>
own functionalities, but cannot cover a more complex and various<br>
scenarios of test-and-set scripting scenarios.<br><br></blockquote></div></div>