4 May
2009
4 May
'09
2:08 p.m.
Hello,
I haven't worked on those functions -- it was in my plan if Jan haven't
started, but I just saw he did some.
I tried to add in tmx module some extensions that might not be that
used, trying to keep tm slimmer rather than getting it a fat pig. Anyone
that wants to add to tmx, just feel free. Some of the current things in
tmx may get in tm, as I am looking at tmx being the container for
applications/functions on top tm.
Cheers,
Daniel
On 05/03/2009 03:48 PM, Juha Heinanen wrote:
daniel,
what should be done with t_load_contacts()/t_next_contacts()? should
they go to module_k/tmx or modules/tm? jan proposed to include them in
modules/tm, but i'm not sure what the current status is.
as we have discussed before, i don't consider the current implementation
of those functions a good one. the reason is the branch structure,
which should be extended with information about status of branches
(used/unused). it does not make sense to keep that in a separate avp.
also, in order to make things more simple to understand, i would also
like to get rid of distinction of request uri and appended branches like
was done in opensips.
perhaps these are already taken care of in sip-router?
-- juha
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla
http://www.asipto.com/