4 dec 2008 kl. 15.02 skrev Henning Westerholt:
On Thursday 04 December 2008, Johansson Olle E wrote:
I noticed that this module has some similarities to the carrierroute
[1] module i maintain for the kamailio project (matching mode,
structure
of the tree..). Do you plan also the merge this to the sip-router
repository later on? If yes, perhaps it makes then sense trying to
merge
both modules then?
Without looking at Alfred's work, I want to throw myself into the
debate...
My general feeling about carrierroute is that it is a bag filled with
candy, but a bit too much for one module. It is very clear that it
fits
someone's business platform. Maybe we should consider breaking it
up in
smaller, more focused modules?
Like the work I began in Asterisk, with breaking up Voicemail. It's
been one huge monolithic module that wasn't very adaptive.
I like small adaptive buildingblocks.
Hi Olle,
thanks for the comments. I agree that its a complicated module, and
one
functions is in there (cr_prime_route) to mainly support the special
needs of
our infrastructure. There exists some functionality that could be
moved to a
new module, for example the config file functionality. But on the
other hand
our admins like to have only one interface for all machines. Another
option
would be to move this failure_route functionality, but this is only
one
function, so there is not much to gain here.
I feel that software has to be easy to understand. If I'm looking for
failover,
I won't look deep into a module called "carrierroute"... So even if it's
only one small function, it irritates my feeling of logic... ;-)
Anyway, enough about that...
/O
_______________________________________________
Serdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/serdev
