On 03 Jul 2014, at 14:21, Alex Balashov <abalas...@evaristesys.com> wrote:
> On 07/03/2014 08:18 AM, Abdelkader Allam wrote: >> Very true Alex, didnt knew about htables, just checking about it, very >> interesting :) The added value of Redis though is that other scripts >> running outside of Kamailio can interact with it and potentially >> interact with kamailio, can an external script have access to htables in >> memory db ? > > Yes, but only rather crudely, via the management interface, i.e. > > http://kamailio.org/docs/modules/4.1.x/modules/htable.html#idp1887744 > > So, I agree that if external access to the raw sampling is desired, htable is > not the best. Yes and no. It's easy to write a simple HTTP interface for htables... I really need per second, not average. I need to react FAST. I think one htable with timestamp for last request per IP and one with number of requests for this timestamp will work. Using REDIS may not be fast enough, but I haven't tried. Redis or memcache would easily handle a situation with multiple proxys. Would memcached or Redis handle this on a per second basis? /O _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
