On Wed, Sep 23, 2020 at 4:17 PM David Villasmil <
david.villasmil.w...@gmail.com> wrote:
> Db_text not being obsoleted: +1
>
>
#metoo
--
Sincerely,
Giovanni Maruzzelli
OpenTelecom.IT
cell: +39 347 266 56 18
___
Users mailing list
t;
>
>
>
> *From:*Users
>
>
> *Date: *Wednesday, September 23, 2020 at 9:50 AM
>
>
> *To: *OpenSIPS users mailling list
>
>
> *Subject: *Re: [OpenSIPS-Users] store data locally
>
>
>
>
>
>
> Hello Liviu,
>
>
>
>
>
> SQLite is the
Date: Wednesday, September 23, 2020 at 9:50 AM
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] store data locally
Hello Liviu,
SQLite is the way to go if you want something standard.
But having the ability to just use a text editor to add/remove/modify
records in db_text is golden
Hello Liviu,
SQLite is the way to go if you want something standard.
But having the ability to just use a text editor to add/remove/modify
records in db_text is golden for me.
I used db_text a lot on embedded platforms.
I would vote against obsolete-ing db_text.
For me, it's easier to use db_text
Thanks Ovidiu, it seem the good way for my case.
Le 22/09/2020 17:44, « Users au nom de Ovidiu Sas »
a écrit :
Hello Alain,
If you don't want to run a full blown db, then you can use db_text
without cacheDB.
The data is cached into memory at startup. If you update the text
e with pleasure.
Regards
De : Users au nom de Liviu Chircu
Répondre à : OpenSIPS users mailling list
Date : mardi 22 septembre 2020 à 15:37
À : OpenSIPS users mailling list
Objet : Re: [OpenSIPS-Users] store data locally
On 22.09.2020 16:09, Alain Bieuzent wrote:
I need to store so
I tend to agree with Liviu. Therefore Ovidiu, please convince us of the
advantages of db_text :-)
Op wo 23 sep. 2020 om 07:58 schreef Liviu Chircu :
> On 22.09.2020 18:42, Ovidiu Sas wrote:
> > If you don't want to run a full blown db, then you can use db_text
> > without cacheDB.
> > The data
On 22.09.2020 18:42, Ovidiu Sas wrote:
If you don't want to run a full blown db, then you can use db_text
without cacheDB.
The data is cached into memory at startup. If you update the text
file, you can re-cache the data [1].
Hi, Ovidiu!
May I segue into discussing some questions that have
I personally like memcached because of it's speed and the availability of
SDKs to work with it in so many languages. These are all good choices tho!
I think the quantity and how frequently your data changes is a big factor.
If you have a lot of data that tends to change, I'd use memcache. If it's
Hello Alain,
If you don't want to run a full blown db, then you can use db_text
without cacheDB.
The data is cached into memory at startup. If you update the text
file, you can re-cache the data [1].
You can also manipulate the data using the avpops module [2].
Or, you can use cacheDB on top of
Memcache is a great fit for this. Load the data in externally or thru
programmatic cache_miss. This method supports a very high rate per second.
Just be sure to consider failure cases. Caches should never be expected to
be right 100% of the time. They need to be expected and allowed to fail
On 22.09.2020 16:09, Alain Bieuzent wrote:
I need to store some data locally but accessible by opensips.
the data is almost 20 records made up of a couple IP: name
From opensips script I want to retrieve the name associated with the
IP (to put in place profiling).
how do you set up this
Hi all,
I need to store some data locally but accessible by opensips.
the data is almost 20 records made up of a couple IP: name
>From opensips script I want to retrieve the name associated with the IP (to
>put in place profiling).
how do you set up this kind of solution without
13 matches
Mail list logo
