17 Jan
2009
17 Jan
'09
4:26 p.m.
On 01/16/2009 03:58 PM, Alex Balashov wrote:
Daniel-Constantin Mierla wrote:
also, worth to mention that this does not add any overhead to the core
of the proxy. It is just a module, if one needs it, can use, otherwise
just don't load...
1.5.0 includes a lot of work in making the core slimmer, moving towards
the core framework design planned to get with sip-router.org project.
Cheers,
Daniel
That way,
one gets the benefit of running jobs that have visibility
into the namespace and state of the proxy and access to script
constructs without having to bother with an internal task scheduler.
But sometime you need access to the internals of
kamailio (openser) and
then you can use this one. It can be a standalone process, so it won't
affect the rest of processing.
Yeah, I know. But from a low coupling / high cohesion design
standpoint, it seems better to deputise ancillary things like
task
scheduling outside of the proxy -- especially if a lot of these things
are anticipated to be cleanup jobs on external databases anyway. Or
maybe you just used those as examples without having a particular need
in mind.
--
Daniel-Constantin Mierla
http://www.asipto.com