Hello,
I am considering to pull out some functions from core and add them to a
new module to be named 'corex (core eXtensions), for few reasons:
- most of the core functions have support for static parameters, some of
them could become more useful if cfg variables (pv + selects) will be
supported there
- then it is easier to export some of these functions to inter-module
API for usage from embedded scripts (lua, perl, ...)
- there are many situations when no core function is used in a config
file (like load balancing cfgs), not loading the code will make the
footprint smaller for embedded system (although, I guess this would be
the least important, the extra size is not that significant).
Why a new module is because it has to stay within the licensing decision
made when we merged ser+kamailio, new core code has to be released under
BSD license, if it is not left under FhG GPL2 (e.g., the case of small
touches to existing code). So if it is gonna be a major copy, it will be
moved with the license, if it is going to be re-coded to support
variables, then will be BSD. With this approach I hope nobody has
anything against, the code can be used like so far.
Any comments?
Cheers,
Daniel
--
Daniel-Constantin Mierla -
http://www.asipto.com
http://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 -
http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 -
http://asipto.com/u/kpw