<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.18.3">
</HEAD>
<BODY>
Hi All,<BR>
<BR>
Following this thread from the start and having myself given it some thinking since I saw the openSIPS additionnal send_rteply module to acheive the same think, I would like to share my own conclusions :<BR>
<BR>
- In order to stay backward compatible, no new function names should be used, both for the scripting language and the C functions used by modules<BR>
- I suggest, in order to asses full compatibility and avoid unexpected results, to use a fallback approach for both tm and sl, but to control this with module parameters, set to NO fallback in order to keep the default behavior. This parameter should impact both C exported function behavior and script exported functions.<BR>
<BR>
Result: By default, everything remains the same. In order to have fallback both ways (from TM -> SL and SL ->TM), just make sure both modules are loaded and set the module parameter to 1 for both. And voila, automagically all modules and script using either SL or TM benefit from the fallback.<BR>
<BR>
On Thu, 2008-11-27 at 15:20 +0100, Klaus Darilion wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Daniel-Constantin Mierla schrieb:
>
> On 11/27/08 13:56, Andrei Pelinescu-Onciul wrote:
>> >From a module, one can always check if a transaction exists (or try
>> t_reply and fallback to sl_send_reply).
>>
> This means all the time to bind to two modules, duplicate some code, etc..
>
>> In this particular case (if I understand correctly the bug report), the
>> fix belongs in the pua module (which IMHO should always use tm
>> anyway).
>>
> registrar has same issue with save(...)
>
> I do not see what confusion would be by t_reply(...) falling back to
> stateless mode. Eventually a different reply code can be used to signal
So, you suggest adding the feature to tm module and then changing pua to
use t_reply?
klaus
> this case, a flags parameter to be used to enforce/relax conditions. I
> am not a fan of functions with similar name and just few differences. It
> is hard to document and IMO creates more confusion.
>
> So, yes, there are alternatives, workarounds, we try to find here the
> best one for the moment.
>
> Cheers,
> Daniel
>
_______________________________________________
Devel mailing list
<A HREF="mailto:Devel@lists.kamailio.org">Devel@lists.kamailio.org</A>
<A HREF="http://lists.kamailio.org/cgi-bin/mailman/listinfo/devel">http://lists.kamailio.org/cgi-bin/mailman/listinfo/devel</A>
</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
<B><FONT SIZE="2"><FONT COLOR="#808080">Jérôme Martin </FONT></FONT></B><B><FONT SIZE="2"><FONT COLOR="#bebebe">| </FONT></FONT></B><B><FONT SIZE="2"><FONT COLOR="#99cc00">LongPhone</FONT></FONT></B><BR>
<B><FONT SIZE="2"><FONT COLOR="#808080">Responsable Architecture Réseau</FONT></FONT></B><BR>
<FONT SIZE="2"><FONT COLOR="#bebebe">122, rue la Boetie | 75008 Paris </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#bebebe">Tel : +33 (0)1 56 26 28 44</FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#bebebe">Fax : +33 (0)1 56 26 28 45</FONT></FONT><BR>
<FONT COLOR="#c0c0c0">Mail :</FONT><FONT COLOR="#99cc00"> </FONT><FONT COLOR="#99cc00"><B><FONT SIZE="2">jmartin</FONT></B></FONT><FONT SIZE="2"><FONT COLOR="#bebebe">@longphone.fr</FONT></FONT><BR>
<FONT COLOR="#c0c0c0">Web :</FONT><FONT COLOR="#99cc00"> <A HREF="http://www.longphone.com">www.longphone.com</A></FONT><BR>
<BR>
<BR>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>