[OpenSIPS-Devel] [OpenSIPS-Users] RFC: new opensips design

[Stefan Sayer]

Hi Bogdan,

o Bogdan-Andrei Iancu [11/07/08 13:32]:
> It is not a request for solution, but a request for current problems! We 
> need to know all the problems that people facing in order to come up 
> with a design that will solve them all.
> 
> Please visit:
>     http://www.opensips.org/pmwiki.php?n=Development.NewDesign
I find this quite interesting. A few comments about async/MT processing:
I also think that completely async processing would bring a lot of
advantages for more complex applications, especially if it is completely
event-driven, and if event handlers can be chained (e.g. priority
handling for events generated by event handlers). Note that in this case
i think process vs. threads does not really matter - if it is really
event driven with local context awareness, then there is no dynamic
creation of threads/processes necessary; in fact there is only as many
threads/processes necessary as there are CPU cores; plus
threads/processes for things that cannot be made async, but for those
mostly no dynamic creation would be necessary (more queue or
producer/consumer style). ipc gets simpler though.

About the scripting language: As much as i would favor python, i don't
know whether clear context separation and MT is possible (because of the
GIL, see http://www.python.org/doc/2.5.2/api/threads.html); but maybe
there has been some progress more recently.

Best Regards
Stefan Sayer

-- 
Stefan Sayer
VoIP Services

stefan.sayer at iptego.com
www.iptego.com

IPTEGO GmbH
Am Borsigturm 40
13507 Berlin
Germany

Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann