Hi,
I'd go for the second option, cleaner.
Once we have a list of core functions to be migrated we could split the
work among the developers.
And of course write a nice migration doc 5.2 => 5.3.
Cheers,
Federico
On Wed, Dec 19, 2018 at 8:50 AM Daniel-Constantin Mierla <miconda(a)gmail.com>
wrote:
Hello,
it was brought into discussions several times in the past about core
functions not accepting variables in the parameters. I think it is time
to update them during the 5.3 release development. For few of them, I
added in the past some alternative function in the corex module (e.g.,
force_send_socket() in core and set_send_socket() in corex module).
So, I see two options:
1) add a function with similar name in corex module and same behaviour
like the one from core
2) remove the function export from the core and export one with the same
name from the corex module
First one will ensure that configs using the functions right now keep
working without any update.
The second one will be better in long term from the point of
documentation (no duplicated docs), but there might be few cases that
would require updates in the config -- iirc, there are some functions
that can get special tokens in the parameters (like forward(uri:host,
uri:port)), they will get an equivalent with variables, but old config
will not be compatible.
Obviously the reason for this email is to ask the developers and users
what would be the preferred way from own point of view.
Cheers,
Daniel
--
Daniel-Constantin Mierla --
www.asipto.com
www.twitter.com/miconda --
www.linkedin.com/in/miconda
Kamailio World Conference - May 6-8, 2019 --
www.kamailioworld.com
Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in
Washington, DC, USA --
www.asipto.com
_______________________________________________
Kamailio (SER) - Development Mailing List
sr-dev(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev