<div dir="ltr">Hi Olle,<div><br></div><div>As you can see from the commit time, it was 1:30 in the morning when I finished the MI command part - my intention being to get this in before the 4.1.0 freeze.</div><div><br></div>
<div>If I had time to look at RPC I might well do, but I don't. The reason I was still working on this at 1:30am was that I had run out of time but I needed the MI commands.</div><div><br></div><div>Regards,</div><div>
<br></div><div>Peter</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 2 October 2013 10:24, Olle E. Johansson <span dir="ltr"><<a href="mailto:oej@edvina.net" target="_blank">oej@edvina.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div>2 okt 2013 kl. 10:53 skrev Peter Dunkley <<a href="mailto:peter.dunkley@crocodilertc.net" target="_blank">peter.dunkley@crocodilertc.net</a>>:</div>
<div class="im"><br><blockquote type="cite"><div dir="ltr">Hello,<div><br></div><div>The systems I have currently use MI commands to control my Kamailio instances. As such, it is more convenient for me to add MI commands to modules I write when I need to control them rather than have some use RPC commands and some MI. I am sure RPC is great, but MI commands work for me. I am bound to get around to switching to RPC one day - once all my other jobs are done ;-)</div>
<div><br></div><div>In the meantime, I have no problem with other people adding RPC equivalents to the modules (both websocket and auth_ephemeral have MI commands) if they need them.</div></div></blockquote></div>There is also a need for a global product management policy. It seems like the move to RPC was decided a long time ago, when MI was declared deprecated.</div>
<div><br></div><div>I would encourage all developers to spend time on developing RPC commands for the MI commands you spend time on, regardless on what you personally use in your platform.</div><div><br></div><div>This is a gentle request, not a requirement - I'm in no position to do that. I am just noticing that it is very confusing to teach and explain to new users why we have MI only here and RPC only there. It just doesn't make much sense.</div>
<div><br></div><div>I would suggest RPC first, then MI if you need it to be the policy.</div><div><br></div><div>Cheers :-)</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>/O</div></font></span><div><div class="h5">
<div><br><blockquote type="cite"><div dir="ltr"><div><br></div><div>Regards,</div>
<div><br></div><div>Peter</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 2 October 2013 08:28, Olle E. Johansson <span dir="ltr"><<a href="mailto:oej@edvina.net" target="_blank">oej@edvina.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div>2 okt 2013 kl. 09:25 skrev Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>>:</div>
<div><br><blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
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.<br></div></blockquote><div><br></div></div>Maybe someone (hint, that's you!) will have to start a wiki page where we list modules and missing RPC commands. I did some work before 4.0 release to add RPC commands, but there are missing pieces around.</div>
<span><font color="#888888"><br></font></span><div><span><font color="#888888">/O</font></span><div><div><br><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000">
<br>
Cheers,<br>
Daniel<br>
<br>
<div>On 10/2/13 3:12 AM, Ovidiu Sas wrote:<br>
</div>
<blockquote type="cite">Hello Peter,
<div><br>
</div>
<div>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).</div>
<div>It would be nice to have them implemented over rpc too.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Ovidiu Sas</div>
<div><br>
On Tuesday, October 1, 2013, Peter Dunkley wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Module: sip-router<br>
Branch: master<br>
Commit: fd9fcd75c222b73a2b70793e5d79c7494f757a1e<br>
URL: <a href="http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=fd9fcd75c222b73a2b70793e5d79c7494f757a1e" target="_blank">http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=fd9fcd75c222b73a2b70793e5d79c7494f757a1e</a><br>
<br>
Author: Peter Dunkley <<a>peter.dunkley@crocodilertc.net</a>><br>
Committer: Peter Dunkley <<a>peter.dunkley@crocodilertc.net</a>><br>
Date: Wed Oct 2 01:30:37 2013 +0100<br>
<br>
modules/auth_ephemeral: Added MI commands for shared secret
management<br>
<br>
- Can add, remove, and display shared secrets with MI commands<br>
- This means you can add/revoke secrets without a restart<br>
<br>
---<br>
<br>
modules/auth_ephemeral/README | 74
++++++<br>
modules/auth_ephemeral/autheph_mod.c | 257
+++++++++++++++++++-<br>
modules/auth_ephemeral/autheph_mod.h | 6 +<br>
modules/auth_ephemeral/authorize.c | 11 +-<br>
.../auth_ephemeral/doc/auth_ephemeral_admin.xml | 68
+++++<br>
5 files changed, 405 insertions(+), 11 deletions(-)<br>
<br>
Diff: <a href="http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=fd9fcd75c222b73a2b70793e5d79c7494f757a1e" target="_blank">http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=fd9fcd75c222b73a2b70793e5d79c7494f757a1e</a><br>
<br>
_______________________________________________<br>
sr-dev mailing list<br>
<a>sr-dev@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
</blockquote>
</div>
<br>
<br>
-- <br>
VoIP Embedded, Inc.<br>
<a href="http://www.voipembedded.com/" target="_blank">http://www.voipembedded.com</a><br>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
sr-dev mailing list
<a href="mailto:sr-dev@lists.sip-router.org" target="_blank">sr-dev@lists.sip-router.org</a>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a>
</pre>
</blockquote>
<br>
<pre cols="72">--
Daniel-Constantin Mierla - <a href="http://www.asipto.com/" target="_blank">http://www.asipto.com</a>
<a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a>
Kamailio Advanced Trainings - Berlin, Nov 25-28; Miami, Nov 18-20, 2013
- more details about Kamailio trainings at <a href="http://www.asipto.com/" target="_blank">http://www.asipto.com</a> -
</pre>
</div>
_______________________________________________<br>sr-dev mailing list<br><a href="mailto:sr-dev@lists.sip-router.org" target="_blank">sr-dev@lists.sip-router.org</a><br><a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
</blockquote></div></div></div><br></div><br>_______________________________________________<br>
sr-dev mailing list<br>
<a href="mailto:sr-dev@lists.sip-router.org" target="_blank">sr-dev@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div><font face="courier new, monospace">Peter Dunkley</font></div><div><font face="courier new, monospace">Technical Director</font></div><div>
<font face="courier new, monospace">Crocodile RCS Ltd</font></div></div>
</div>
_______________________________________________<br>sr-dev mailing list<br><a href="mailto:sr-dev@lists.sip-router.org" target="_blank">sr-dev@lists.sip-router.org</a><br><a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
</blockquote></div><br></div></div></div><br>_______________________________________________<br>
sr-dev mailing list<br>
<a href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div><font face="courier new, monospace">Peter Dunkley</font></div><div><font face="courier new, monospace">Technical Director</font></div><div>
<font face="courier new, monospace">Crocodile RCS Ltd</font></div></div>
</div>