From: Eliezer Croitoru Date: 2012-07-12T01:18:52+09:00 Subject: Re: the best way to match these domains. On 7/11/2012 10:49 AM, Jes�s Gabriel y Gal�n wrote: > On Wed, Jul 11, 2012 at 9:22 AM, Eliezer Croitoru wrote: >> does it support indexing?reverse indexing? > > It's basically a key - value data store, in which the value can be a > data structure: string, list, hash, set, sorted set, with first level > support for atomic operations on those values: add to a set, get the > highest score value in a sorted set, etc. > So, no, it doesn't support indexing as you would think about indexes > in a relational database. But if your data structures fit one of the > supported types, your life is made a lot easier out of the box. > > Jesus. > Thanks, i indeed looked at it. it seems to fit my cache needs but not the filtering. it really simplified many things for me with the "expire"(setex) method. i need to store maximum of 3-6 minutes the key and the url so it fit's like hell to me. for a more robust lookups i need DB and i can cache the results in redis because it's a one way ticket per domain for a long time. i can add a domain result for half a day and it will do a really good work. my main problem is that i am using forks and redis ruby library dont like it. and also my eventmachine server has a "clenup" nasty method that releases any old object when ending session so i do have a problem with it. if you have an idea on how to handle REDIS with forks i will be so happy. Thanks, Eliezer -- Eliezer Croitoru https://www1.ngtech.co.il IT consulting for Nonprofit organizations eliezer ngtech.co.il