Hello,
for clarification, mi framework was switched to use system malloc
for several releases now, then internal memory manager can avoid
fragmentation with mem_join parameter. So this is not a reason for
not doing mi. However, it would be good if at a point we can get to
a single control interface, rpc has more transports and is more
standard approach.
Cheers,
Daniel
On 10/2/13 3:12 AM, Ovidiu Sas wrote:
Hello Peter,
I noticed that you added some new MI commands. Because the
MI interface is causing memory fragmentation, the use or rpc
commands is preffered over MI and the use of MI interface is to
be deprecated in the near future (once all MI commands are
ported to rpc).
It would be nice to have them implemented over rpc too.
Regards,
Ovidiu Sas
--
VoIP Embedded, Inc.
http://www.voipembedded.com
_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Nov 25-28; Miami, Nov 18-20, 2013
- more details about Kamailio trainings at http://www.asipto.com -