<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I use a lot of applications. :)<br>
<br>
So the mix/match syntax below is 'pretty fine' for you?<br>
<br>
- #!define NAME VALUE<br>
- NAME "VALUE"<br>
- NAME=VALUE<br>
- NAME="VALUE"; # required quotes are parameter specific<br>
<br>
As a user, it can be painful figuring which syntax to use just to
set a simple name/value pair. Each method is basically equivalent
in functionality, but only one will work. And that depends on where
it's used in the configuration. This is what I really want to fix.<br>
<br>
And don't forget, there's one more way we can set a name/value pair.<br>
<br>
modparam("module_name", "NAME", "VALUE")<br>
<br>
Changing the routing logic seemed to be the easiest to address,
starting with an include. With the simple goal of separating
logic{..} from configuration directives. <br>
<br>
My thought here.. In order to fix the name/value syntax, leave the
current configuration parser untouched for routing logic. But
first, we have to separate the routing logic from the main
configuration file.<br>
<br>
Adding a compile option is just a longer term vision for a cleaner
configuration structure. A directory provides the user flexibility,
but a fixed routing_logic.cfg file works too. But even a fixed file
should be customizable as a compile option.<br>
<br>
<br>
Sincerely,<br>
Brian LaVallee<br>
<br>
<br>
<div class="moz-cite-prefix">On 3/19/15 19:33, Alekzander Spiridonov
wrote:<br>
</div>
<blockquote
cite="mid:CA+=mPaqFw1zY5R5y7x0EnvCT6mTP2KijDA+3gLYRVBX46+P0ow@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>=D I believe you've learned too many applications. <br>
<br>
</div>
Current syntax looks pretty fine for me and (as you've already
mentioned) any separation could be achieved with include's.<br>
<br>
</div>
Anyway I'm strongly against idea of any compile-time paths.<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2015-03-19 10:13 GMT+03:00 Brian
LaVallee <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:brian.lavallee@invite-comm.jp"
target="_blank">brian.lavallee@invite-comm.jp</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hi,<br>
<br>
I would like to propose [and manage] an effort with the
primary Kamailio developers to simplify the configuration
syntax. I'm not a developer, but used lot's of different
applications and I'm familiar with various configuration
formats.<br>
<br>
Based on what I've seen, there are five (5) types of
configuration directives used with Kamailio. <br>
<br>
- C-Style Control Directives<br>
- Apache-Like Name/Value Pairs<br>
- Normal Name/Value Pairs<br>
- Modify Parameter Procedures<br>
- Routing Logic Scripting<br>
<br>
I do understand some of this may be the result of merging
multiple projects. But this mixture of syntax slows
adoption, drastically increases the learning curve for the
user base. By implementing a consistent standard to the
configuration syntax, it will make using the application
less complicated.<br>
<br>
--<br>
<br>
My first recommendation, would be to separate the routing
logic from the primary configuration file. This can
easily be done with import/include. However, I feel that
a fixed path should be added during compile. <br>
<br>
‘<samp>--with-routing=/etc/kamailio/routing/</samp>’<br>
<br>
Then it would possible to modify the configuration parser
to read all the files in that directory. Allowing the
separation of the route logic into individual files.
relay.cfg, reqinit.cfg, ... xmlrpc.cfg, tovoicemail.cfg,
etc... Making individual logic changes a bit easier.<br>
<br>
To reach a fixed path solution, and keep some backwards
compatibility, the first step should be... Use
import/include and move all the route logic into
/etc/kamailio/routing/basic.cfg<br>
<br>
We can discuss on the mailing list or feel free to contact
me directly.<br>
<br>
<br>
Sincerely,<br>
Brian LaVallee </div>
<br>
_______________________________________________<br>
sr-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a><br>
<a moz-do-not-send="true"
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">
<br>
-- <br>
<div class="gmail_signature">
<div>
<div>Best regards,<br>
Alekzander Spiridonov</div>
<br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
sr-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>