[Devel] Race conditions in TM, SER implementation, etc...

[Bogdan-Andrei Iancu]

I think we miss the logical factor.

you want a debate about a warning message on which nobody had no 
evidence (except speculations) that causes problems ...Is any problem or 
crash reported on that?

otherwise, I see another discussion "SER vs OpenSER" which I really want 
to avoid as nothing good came out of this ....ever. As I posted couple 
of days ago, my interest is only in OpenSER and I do not have 
expertise/will/interest any more to formulate any opinions on SER. 
Please accept it as it is.

sorry, but you get a "603 Decline" from my side.

regards,
bogdan


Jerome Martin wrote:
> Hi list,
>
> I'm starting this as a new topic, because I'd really want to be able 
> to assess the risk I'm taking by using OpenSER vs SEr (I don't intend 
> to move to SER right now, however it would be good knowing exactly the 
> weaknesses  of OpenSER, as I'm using it in production right now).
>
> What I'm interested in is understanding something Jiri is explaining 
> about race conditions in tm, about that probleme being fixed in last 
> SER cvs but still present in OpenSER 1.2 despite all the work by 
> Bogdan on timers etc...
>
> Firsthand : Jiri, is that right or did I misunderstood what you've said ?
>
> Looking at both SER cvs and OpenSER, I see comments pointing to a 
> possible race condition here and there, typically in timer.c.
> So could anyone point me to the "risky operations" on timers that 
> would lead to race conditions with noticeable side-effects that still 
> exist in OpenSER but are solved in SER ?
> What would those side effects be ?
> Is that a locking-related issue, or is it a deeper structural problem ?
>
> Bogdan, what do you think ?
>
> Best Regards,
> Jerome
>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Devel mailing list
> Devel at openser.org
> http://openser.org/cgi-bin/mailman/listinfo/devel
>