>> *From:* sr-users on behalf of Olle
>> E. Johansson
>> *Sent:* Wednesday, December 19, 2018 2:38 PM
>> *To:* Daniel-Constantin Mierla
>> *Cc:* Kamailio (SER) - Development Mailing List; Kamailio (SER) - Users
>> Mailing List
>> *Subj
-Users] [sr-dev] RFC: updates to some core functions
> On 19 Dec 2018, at 12:26, Daniel-Constantin Mierla wrote:
>
>
> On 19.12.18 09:47, Olle E. Johansson wrote:
>>
>>> On 19 Dec 2018, at 09:41, Daniel-Constantin Mierla
>>> wrote:
>>>
>>> corex
, 2018 11:25 AM
To: Kamailio (SER) - Development Mailing List
Cc: sr-us...@lists.kamailio.org
Subject: Re: [SR-Users] [sr-dev] RFC: updates to some core functions
Going back one step, are there any reasons to keep tmx, kex and corex modules
at all?
At this point in the project I think many
I prefer second way. Without any duplication.
For old configs branches 4.4, 5.0, 5.1 is always available.
Sergey
ср, 19 дек. 2018 г. в 10:50, Daniel-Constantin Mierla :
> Hello,
>
> it was brought into discussions several times in the past about core
> functions not accepting variables in the
Pflichtangaben:
>> http://www.ng-voice.com/imprint/ <http://www.ng-voice.com/imprint/>
>>
>> Am Mi., 19. Dez. 2018 um 12:55 Uhr schrieb YAS0 CANER
>> mailto:caner_y...@hotmail.com>>:
>> TmEXIT , kEXIT and corEXIT is failed
>> From: sr-
ANER <
> caner_y...@hotmail.com>:
>
>> TmEXIT , kEXIT and corEXIT is failed
>> --
>> *From:* sr-users on behalf of Olle
>> E. Johansson
>> *Sent:* Wednesday, December 19, 2018 2:38 PM
>> *To:* Daniel-Constantin Mier
lto:o...@edvina.net>>
> Sent: Wednesday, December 19, 2018 2:38 PM
> To: Daniel-Constantin Mierla
> Cc: Kamailio (SER) - Development Mailing List; Kamailio (SER) - Users Mailing
> List
> Subject: Re: [SR-Users] [sr-dev] RFC: updates to some core functions
>
>
>
XIT and corEXIT is failed
> --
> *From:* sr-users on behalf of Olle
> E. Johansson
> *Sent:* Wednesday, December 19, 2018 2:38 PM
> *To:* Daniel-Constantin Mierla
> *Cc:* Kamailio (SER) - Development Mailing List; Kamailio (SER) - Users
> Mailing List
>
> On 19 Dec 2018, at 12:26, Daniel-Constantin Mierla wrote:
>
>
> On 19.12.18 09:47, Olle E. Johansson wrote:
>>
>>> On 19 Dec 2018, at 09:41, Daniel-Constantin Mierla
>>> wrote:
>>>
>>> corex module was added to hold the functions that otherwise would be
>>> more or less "in the core",
On 19.12.18 09:47, Olle E. Johansson wrote:
>
>> On 19 Dec 2018, at 09:41, Daniel-Constantin Mierla wrote:
>>
>> corex module was added to hold the functions that otherwise would be
>> more or less "in the core", like those that were updated to support
>> variables in the parameters, so this is
On 12/19/18 3:18 AM, Victor Seva wrote:
On Wed, 19 Dec 2018 at 08:49, Daniel-Constantin Mierla
mailto:mico...@gmail.com>> wrote:
2) remove the function export from the core and export one with the same
name from the corex module
This would be my preference as well.
--fred
> On 19 Dec 2018, at 09:41, Daniel-Constantin Mierla wrote:
>
> corex module was added to hold the functions that otherwise would be
> more or less "in the core", like those that were updated to support
> variables in the parameters, so this is the one to take the place of
> core in regard to
corex module was added to hold the functions that otherwise would be
more or less "in the core", like those that were updated to support
variables in the parameters, so this is the one to take the place of
core in regard to exporting functions.
tmx was added because tm module became very big, but
Going back one step, are there any reasons to keep tmx, kex and corex modules
at all?
At this point in the project I think many of the functions should be merged
into
the main modules and core.
If I remember correctly, they exist because of a multi-brand history that is not
really the case
Am Mittwoch, 19. Dezember 2018, 09:03:26 CET schrieb Sergey Safarov:
> I prefer second way. Without any duplication.
> For old configs branches 4.4, 5.0, 5.1 is always available.
Hello,
I would prefer also the second way, for the same reason: less duplicated
functions.
Best regards,
Henning
15 matches
Mail list logo
