What about the issues I had with serial forking that I wrote to you
about? Will they make it into 1.6.4?
You fixed the core functionality so that serial forking worked somewhat,
but to get my "dream scenario", I needed some tweaks for the
return-codes of of serialize_branches.

This is what I wrote:

        A few notes though. It seems like I need the serialize_branches()
        to return a useful returncode as well. Otherwise my script cannot
        differentiate between when serialforking really is being done, or
        when normal proxy or parallell fork is in progress. (In which case
        I wanted normal timer C) Returning 1 in the end of serialize.c, ยด
        instead of 0 which is returned when nothing is performed by the call
        to serialize_branches() took care of that.
        This cause action.c do LOG_ERR though, so I changed that to only
        log error if the return from serialize_branches was < 0.

Regards
Taisto Qvist



On Tue, 14 Dec 2010 15:21:46 +0200, Bogdan-Andrei Iancu <[email protected]> wrote:
Hi everyone,

we are in full progress of fixing the last bugs, of doing all
backports from devel version, of uploading the last patches.....and
testing :) for the new release.

In the next days I will compile a list of all changes and
improvements of this release - I will send you the link once ready.

From timeline point of view :

   - Wednesday 15 Dec - hour 24:00 UTC - SVN freeze
   - testing and packaging update
   - *Monday 20 Dec - official release*.

If there are things missing to this new release (code, patches, docs,
anything), please let me know.


Best regards,
Bogdan

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

--
Taisto Qvist, IP-Solutions
Mobile: +46-708-88 02 63
"We are Pentium of Borg. Division is futile, You will be approximated"

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to