<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1251">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Hello,</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
i agree with Mr. Johansson . Merging main modules and cores help to find right function in documentation. </div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Thanks</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<span style="color: rgb(51, 51, 51); font-family: "Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif; font-size: 14.6667px; background-color: rgb(255, 255, 255); display: inline !important">/O</span><br style="color: rgb(51, 51, 51); font-family: "Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif; font-size: 14.6667px; background-color: rgb(255, 255, 255)">
<span style="color: rgb(51, 51, 51); font-family: "Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif; font-size: 14.6667px; background-color: rgb(255, 255, 255); display: inline !important">“The
campaign to remove Kamailio extensions to Kamailio”</span><br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> sr-users <sr-users-bounces@lists.kamailio.org> on behalf of Olle E. Johansson <oej@edvina.net><br>
<b>Sent:</b> Wednesday, December 19, 2018 11:25 AM<br>
<b>To:</b> Kamailio (SER) - Development Mailing List<br>
<b>Cc:</b> sr-users@lists.kamailio.org<br>
<b>Subject:</b> Re: [SR-Users] [sr-dev] RFC: updates to some core functions</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText">Going back one step, are there any reasons to keep tmx, kex and corex modules at all?<br>
<br>
At this point in the project I think many of the functions should be merged into <br>
the main modules and core. <br>
<br>
If I remember correctly, they exist because of a multi-brand history that is not<br>
really the case any more.<br>
<br>
/O<br>
“The campaign to remove Kamailio extensions to Kamailio”<br>
<br>
<br>
> On 19 Dec 2018, at 09:11, Henning Westerholt <hw@kamailio.org> wrote:<br>
> <br>
> Am Mittwoch, 19. Dezember 2018, 09:03:26 CET schrieb Sergey Safarov:<br>
>> I prefer second way. Without any duplication.<br>
>> For old configs branches 4.4, 5.0, 5.1 is always available.<br>
> <br>
> Hello,<br>
> <br>
> I would prefer also the second way, for the same reason: less duplicated <br>
> functions.<br>
> <br>
> Best regards,<br>
> <br>
> Henning<br>
> <br>
> <br>
>> ñđ, 19 äåê. 2018 ă. â 10:50, Daniel-Constantin Mierla <miconda@gmail.com>:<br>
>>> Hello,<br>
>>> <br>
>>> it was brought into discussions several times in the past about core<br>
>>> functions not accepting variables in the parameters. I think it is time<br>
>>> to update them during the 5.3 release development. For few of them, I<br>
>>> added in the past some alternative function in the corex module (e.g.,<br>
>>> force_send_socket() in core and set_send_socket() in corex module).<br>
>>> <br>
>>> So, I see two options:<br>
>>> <br>
>>> 1) add a function with similar name in corex module and same behaviour<br>
>>> like the one from core<br>
>>> <br>
>>> 2) remove the function export from the core and export one with the same<br>
>>> name from the corex module<br>
>>> <br>
>>> First one will ensure that configs using the functions right now keep<br>
>>> working without any update.<br>
>>> <br>
>>> The second one will be better in long term from the point of<br>
>>> documentation (no duplicated docs), but there might be few cases that<br>
>>> would require updates in the config -- iirc, there are some functions<br>
>>> that can get special tokens in the parameters (like forward(uri:host,<br>
>>> uri:port)), they will get an equivalent with variables, but old config<br>
>>> will not be compatible.<br>
>>> <br>
>>> Obviously the reason for this email is to ask the developers and users<br>
>>> what would be the preferred way from own point of view.<br>
>>> <br>
>>> Cheers,<br>
>>> Daniel<br>
> <br>
> <br>
> -- <br>
> Henning Westerholt - <a href="https://skalatan.de/blog/">https://skalatan.de/blog/</a><br>
> Kamailio services - <a href="https://skalatan.de/services">https://skalatan.de/services</a><br>
> Kamailio security assessment - <a href="https://skalatan.de/de/assessment">https://skalatan.de/de/assessment</a><br>
> <br>
> _______________________________________________<br>
> Kamailio (SER) - Development Mailing List<br>
> sr-dev@lists.kamailio.org<br>
> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
<br>
<br>
_______________________________________________<br>
Kamailio (SER) - Users Mailing List<br>
sr-users@lists.kamailio.org<br>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</div>
</span></font></div>
</body>
</html>