I was overwhelmed after a short introduction to CouchDB. But as I
couldn't find a Java API that met my requirements I took the top level
consumer API from BananaDB and applied it to CouchDB. It works
extremly well according to me.
CouchDB is however quite a different project compared to BananaDB.
BananaDB is a bunch of files with a locking mechanism, CouchDB is a
real DBMS. They both have their use cases and I think it's worth
saving the BananaDB core and consumer API as an own project rather
than hiding it as a tag in the SVN.
I'd take this new project to the CouchDB-sandbox if it existed, but it
doesn't and even though their plan is to add such an area I've been
told it will only accept Erlang code. So I'd still like to host this
new (and so far nameless) CouchDB java-bindings project as a new lab.
If you people agree with this beeing OK, how should I proceed? Just
pop this message in the BananaDB trunk and change some flag in the
DAOP and ask for a vote on a new project?
karl
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
