[Serdev] SER as an extendable codebase/SIP stack - was: So who/what is SER for, anyway?

[Greger V. Teigre]

>> There are already good SIP stacks out there to add one more. But I think
>> that standard functionality should be part of the core and all the
>> control that is needed is in the form of flags and variables (I don't
>> see why anyone would want to write a script that implements another
>> transaction state machine as the RFC one).
>>     
>
>   I have a different opinion on this. SER core should stay as a simple
>   message forwarder. There are certainly things that can be made better,
>   such as the tm interface (functions called in the script), dialog
>   support, and handling of multiple downstream branches, but in
>   principle I think the current mechanism of implementing the routing
>   logic in the script is right.
>   
I agree with Jan on this.
g-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.iptel.org/pipermail/serdev/attachments/20070129/16b410db/attachment.html