<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Hi Michael</tt>,<br>
<br>
On 02/10/2013 10:42 AM, Michael Renzmann wrote:
<blockquote
cite="mid:915927f5-6358-4156-97cd-cfb2cca31c7d@email.android.com"
type="cite">Hi Bogdan.<br>
<br>
1. Though nothing that necessarily is bound to a new release:
documentation improvements would be a big deal. Just the very
first example that comes to mind here is an explanation of the
meaning of the various flags in avpops module.<br>
</blockquote>
Agree - some docs (especially avpops) should be updated. Also we
have on the pipe some more tutotials on how to do things like DR,
NAT, etc.<br>
<br>
<blockquote
cite="mid:915927f5-6358-4156-97cd-cfb2cca31c7d@email.android.com"
type="cite">
<br>
2. Not an entirely new feature, but still: for avp_load(), allow
to specify an optional prefix that is prepended to all AVPs
created by avp_load, as you recently suggested. That is: prefix
"callee_" would a usr_preference "channels_inbound" to end up in
$avp(callee_channels_inbound).<br>
</blockquote>
This is on the list !<br>
<blockquote
cite="mid:915927f5-6358-4156-97cd-cfb2cca31c7d@email.android.com"
type="cite">
<br>
3. Related to 2: for avp_load(), allow to specify an optional
(regex or glob) filter to control which of the loaded values are
made available as AVP. This is probably a very special thing and
has limited use-cases, but still...<br>
</blockquote>
Well, as the filtering will be done by apvops module (and not by the
DB driver), filtering may not bring too much value (as you already
loaded the data) - you could simply load all and ignore whatever you
do not need. :) .<br>
<br>
Anyhow, I will add this as low prio. <br>
<br>
Regards,<br>
Bogdan<br>
<br>
<blockquote
cite="mid:915927f5-6358-4156-97cd-cfb2cca31c7d@email.android.com"
type="cite">
<br>
Bye, Mike<br>
<br>
<div class="gmail_quote">Bogdan-Andrei Iancu
<a class="moz-txt-link-rfc2396E" href="mailto:bogdan@opensips.org"><bogdan@opensips.org></a> wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap: break-word; font-family: monospace; margin-top: 0px;">Hi all,
According the the release policy
(<a moz-do-not-send="true" href="http://www.opensips.org/Development/Development">http://www.opensips.org/Development/Development</a>), I would like to call
for a brainstorming, ideas, discussion, etc regarding what should be the
roadmap for OpenSIPS 1.10 - more or less, what new goodies should be in
1.10 release (next major release).
The page is already ready (<a moz-do-not-send="true" href="http://www.opensips.org/Main/Ver1100">http://www.opensips.org/Main/Ver1100</a>) and
pre-populated with the pending items from 1.9 release plus some items
from my side .
I would like to stat the discussion here, on the mailing list first, to
get from all community ideas on what should be done in 1.10 - things to
improve, supporting new RFC/drafts, new functionalitites, etc.
So, please do not be shy and make
your points here ;).
Also we plan a second round of discussion / selection via an IRC meeting
(probably in 2 weeks or so).
Best regards,
</pre>
</blockquote>
</div>
<br>
-- <br>
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
gesendet.
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
</body>
</html>