ya, that's crowded, but the name of this project is very appropriate, because we use memcache protocol and db, and benefit from memcached's original code for its honor.
On 9/29/07, Paul Querna <[EMAIL PROTECTED]> wrote: > Small request: Is it possible to use a different project name? > > The whole memcache* namespace is becoming quite crowded. > > (libmemcache, libmemcached, memcachedb, etc etc) > > -Paul > > > Steve Chu wrote: > > ChangeLog: > > * add command "flush_all" that will truncate a database, warning to use. > > * lots of code formated > > * Bugfix: Now using "-u" option can get proper db file mode > > > > see: http://code.google.com/p/memcachedb/wiki/ChangeLog > > > > ---------- > > > > What is Memcachedb? > > > > Memcachedb is a distributed storage system designed for persistent. We > > simplely hacked from memcached and tugela. But neither of them. > > Memcachedb is not a cache solution, it is a persistent solution for > > high-frequency writing and reading. It conforms to memcache > > protocol(not completed, see below), so any memcached client can have > > connectivity with memcachedb. Memcachedb uses Berkeley DB as a storing > > backend, so lots of features including transaction and replication are > > supported. > > Memcachedb Features > > > > * High network performance, thanks to memcached and libevent(we > > using epoll). > > * High storage performance, Using Berkeley DB BTREE Access Method, > > and bdb's own MPOOL. > > * High availability, Berkeley DB Transaction supported, and > > replication will be ready later. > > > > Supported memcache command > > > > * get, set, add, replace > > * incr, decr > > * delete > > * stats > > * flush_all > > > > Private commands > > > > * db_checkpoint > > * db_archive > > > > We Stand on the shoulders of giants, Memcachedb source code is based on: > > > > * Memcached: http://www.danga.com/memcached/ > > * Tugela: http://meta.wikimedia.org/wiki/Tugela_Cache > > > > > > -- Steve Chu http://stvchu.org -- Steve Chu http://stvchu.org
