On Mon, Nov 27, 2017, at 08:55 AM, Nir Simionovich wrote: > @corey, > > I've been looking into res_sorcery_astdb, but I think I'm missing > something in here. > If I would create a a redis backend for sorcery, the functionality is > fairly limited in the scope > of Redis usage. Mainly due to the fact that sorcery is meant as a CRUD > interface. > > Have I got it correct?
It ultimately depends on the use case and what exactly is trying to be achieved. As with any general interface (like sorcery) the result is that you are somewhat limited to what the interface provides, but the benefit being it can be used by anything that uses the interface. Is it worth it? Could be as Corey mentioned. If your goal, however, is to provide all the knobs and possibilities that redis can do - then it obviously wouldn't be a good fit. -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com & www.asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
