2009/8/24 Alex Balashov <abalashov(a)evaristesys.com>om>:
Please be careful amidst all this to remember that
this "integration" could
be the undoing of the Kamailio/SR project, and may drive people to OpenSIPS.
In the end, it is the users that matter.
The
sip-router.org documentation is already excessively complicated and
difficult to understand for anyone who does not routinely work with both the
K and S code. At this point, the documentation, while voluminous, is
overwhelming and, in places, woefully incomplete, while in other places, I
would say "exhaustively" (perhaps "exhaustingly") complete.
All of this confusion - starting with the fundamental difference between K
and SR, which nobody *I* know in the user community yet understands in any
level of substance or detail - is starting to make OpenSIPS look very
straightforward and self-evident. You don't want this.
I also encounter the widespread perception from my customers that a lot of
time has been spent on "fun" and "interesting" integration work, not
on
developing features or fixing bugs. I hope they're wrong.
I must agree with Alex.
Sincerely I will wait until SR is really released to start with it.
And with "really released" I mean: when both kamailio and SER concepts
disapear entirely from SR (no more K/S-modules, K/S-functions,
K/S-components, K/S-pseudovariables, no more compability features and
so on).
What I don't understand is the reasons to make current SR working with
K and S features/modules compatibility. We don't need a SR working
solution right now (since Kamailio and SER do exist), do we?. Wouldn't
be better to spent devel time in porting the required K/S modules to
SR instead of making them working as K/S modules in any way?
Please, don't take me wrong, I just wonder what's the rush to have a
SR working instead of having a real an independent SR release :)
--
Iñaki Baz Castillo
<ibc(a)aliax.net>