Responses below. On Mon, Jul 23, 2012 at 6:38 PM, Geoffrey Hoffman <[email protected]> wrote: > It only takes 2 minutes longer to post a relevant message specific to > memcached and avoid cross posting.
When you obsessively edit emails like I do, it takes a lot longer than 2 minutes :-). But yes, sorry about that. The project is largely memcached-based at the moment. Memcached is the only cache implementation, and is the canonical (i.e. most recently updated) database backend as well. Gobpersist is irrelevant to many of the current memcached uses, since it's a database cache, rather than a rendered data cache. (It seems like mostly people are using memcached for the latter, though I could be wrong; I don't know the community that well.) But hopefully this will open up memcached to new uses. We'll see. > > That said, your stuff seems pretty cool. I wondered WTH Tokyo Tyrant was and > went to their page, where it says, > >> BTW, do you know Kyoto Tycoon? Actually, it is more powerful and >> convenient server than Tokyo Tyrant. At this distance of time, Kyoto Tycoon >> surpasses Tokyo Tyrant in every aspects. I strongly recommend you to use >> Kyoto Tycoon. AFAIK, Kyoto Tycoon has not seen a lot of usage, due to licensing issues/fears (GPL vs. LGPL). I'm also not so sure that the author has actually improved it over Tokyo Tyrant, which is already very simple and amazingly fast. Normally I'd be pretty reticent to continue to use something with that sort of message on the home page, but this seems to be a weird situation where next gen. didn't take and Tokyo Tyrant still actually has more community support than Kyoto Tycoon. > Any sample usage? How to add Redis? I would extend Field class? Lot's of examples in the docs. But yeah; maybe I should add a quick complete example to the front page? I'll do this soon. To add Redis, you'd need to write a new back end. Like I said, I've yet to document how to do that, but if you want to get on it, you can look at the MemcachedBackend class in gobpersist.backends.memcached. The tokyo tyrant back end is more like what you want (there's a few spaces where the memcached back end is lax since it expects stuff to go out of cache and vanish arbitrarily), but it hasn't yet been altered to subclass from gobkvbackend, which is there to make the life of a back end developer much easier. If you want to do this, definitely stay in touch. I'd be happy to help out answering questions and see if we can't get the code included. Thanks, Evan
