@Alan,
I've looked into both implementations - let's put it this way, both are
highly opinionated in terms of how things
need to be done. The func_redis implementation isn't bad, API wise, however
- the concept of having just
one possible Redis in the config is highly counter productive.
I
Regarding the func_redis module linked here - I contributed a couple of
patches to it and I spoke to Sergio (the original author) and he is no
longer associated with the IT Departament of the University of La Laguna
Tenerife Spain, who currently owns this repository. He says that the
current
I hope we consider creating a res_redis first, then base everything off
that. If a redis library can be used directly by any module that would
fine but I'd like to see us avoid following the example of curl where
everything uses a dialplan function to perform requests. Dialplan
functions
Well,
We can start with that implementation as a base for learning, and go from
there. Looks like I have some homework for tonight.
Nir
On Fri, Dec 22, 2017, 18:44 Matt Fredrickson wrote:
> On Fri, Dec 22, 2017 at 10:23 AM, Ivan Poddubny
> wrote:
On Fri, Dec 22, 2017 at 10:23 AM, Ivan Poddubny
wrote:
> Hi,
>
> There is an out-of-tree implementation of func_redis: https://github.
> com/tic-ull/func_redis.
> I don't use it in production, but it worked fine for me on a test machine.
> With slight modifications it
Hi,
There is an out-of-tree implementation of func_redis:
https://github.com/tic-ull/func_redis.
I don't use it in production, but it worked fine for me on a test machine.
With slight modifications it works with Asterisk 13+.
Unfortunately, the project seems to be abandoned and the author did not
On Fri, Dec 22, 2017 at 6:58 AM, Nir Simionovich
wrote:
> Abhay,
>
> Migrating astsb from SQLlite to redis isn't the topic here. I'm talking
> adding a new type of storage engine. For example, func_redis, that will
> implement the relevant key/value operations that are
Hi,
On 12/22/2017 7:22 AM, Nir Simionovich wrote:
Every, and I do mean every, Asterisk application requires a
key/value store of some form. Most developers will
basically butcher (would have used stronger words, but refraining from
doing so) AstDB in the process, which will
then result in a
I would have an immediate use case for something like func_redis. I think it
would be very useful.
On December 22, 2017 at 8:02:28 AM, Nir Simionovich (nir.simionov...@gmail.com)
wrote:
Abhay,
Migrating astsb from SQLlite to redis isn't the topic here. I'm talking adding
a new type of
On Fri, Dec 22, 2017 at 5:22 AM, Nir Simionovich
wrote:
> Hi All,
>
> Following a discussion on JIRA [https://issues.asterisk.org/
> jira/browse/ASTERISK-27383], I truly believe that
> adding a scaleable, robust and most importantly - accepted key/value store
>
Abhay,
Migrating astsb from SQLlite to redis isn't the topic here. I'm talking
adding a new type of storage engine. For example, func_redis, that will
implement the relevant key/value operations that are commonly used by
people.
Nir
On Fri, Dec 22, 2017, 14:33 Abhay Gupta
Hi All,
I had a program where I have implemented a project using REDIS wherein the
client is made using a socket library and no other third party client library
in C .
This REDIS database has 400 million records and performs extremely well though
the memory requirement for such a large
Hi All,
Following a discussion on JIRA [
https://issues.asterisk.org/jira/browse/ASTERISK-27383], I truly believe
that
adding a scaleable, robust and most importantly - accepted key/value store
mechanism to the Asterisk dialplan
is a worthwhile effort.
Every, and I do mean every, Asterisk
13 matches
Mail list logo