Hi all,<br><br>Concerning portability again :-)<br><br>Is there any way I can add in the memory all the numbers with portability? (2.000.000 rows)?<br>And also reload these data a few times a day and access this data from the Kamailio script?<br>
<br> Cheers<br>Alex<br><br><br><br><div class="gmail_quote">On Tue, Dec 22, 2009 at 12:56 AM, Henning Westerholt <span dir="ltr"><<a href="mailto:henning.westerholt@1und1.de">henning.westerholt@1und1.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Mon, December 21, 2009 9:50 pm, Alex Balashov wrote:<br>
> [..]<br>
<div class="im">> Having said that, AVPs are still very useful and necessary because they<br>
> persist across the lifetime of a transaction, so you can access them in<br>
> subsequent reply and failure routes. This is not true of user<br>
> pseudovariables ($var(...)), nor, as far as I know, of any other class<br>
> of pseudovariable at this point except special transaction-persistent<br>
> ones exported by modules.<br>
><br>
> As a result, it is often necessary for me to take data from $dbr<br>
> (sqlops) and load it into arrays of AVPs, such as for example when doing<br>
> custom fail-over in failure_route that uses logic for which dispatcher<br>
> is not suitable. I store a set of gateways in an AVP array along with<br>
> another AVP value indicating the current array index and iterate over<br>
> them in failure_route, and so on.<br>
><br>
> Daniel taught me how to use AVP arrays once, although I noticed this is<br>
> not mentioned anywhere in the avpops documentation. It should be<br>
> published somewhere, as it is one of the most useful programmatic<br>
> features of Kamailio.<br>
><br>
> Henning/Daniel, does Kamailio 3/SR offer any kind of better substitute<br>
> for what I am doing with AVPs as described above? In other words, are<br>
> there any transaction-persistent pseudovariables and/or namespace<br>
> containers that are easier to deal with syntactically, and provide more<br>
> advanced data structure primitives like arrays? I am aware of htable,<br>
> but I need something local to a transaction, not global.<br>
<br>
</div>There are the $var PVs you already mentioned, and then also the $shv that<br>
are shared variables. But they are (process) global, and not<br>
transactional. Daniel proposed and developed the new xavp type for sr<br>
which are basically extended AVPs. More informations can be found here:<br>
<a href="http://sip-router.org/wiki/devel/xavp" target="_blank">http://sip-router.org/wiki/devel/xavp</a><br>
<br>
Regards,<br>
<font color="#888888"><br>
Henning<br>
<br>
</font></blockquote></div><br>