couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Klaus Trainer <>
Subject Re: splitting the code in different apps or rewrite httpd layer
Date Sun, 22 Aug 2010 20:51:00 GMT
> It seems that noone except us is interrestted in that ;)

I'm indeed very interested in that. However, as I won't be able to
contribute much to the refactoring, I didn't feel like having to say
something in this regard. So, nonetheless, here are my two cents.

Recently, I've spent a few hours diving into the source code of riak and
riak_core. In doing so, I got the impression that with regard to
modularization and organizing the codebase around the abstractions, the
Riak guys are one step ahead in respect of their codebase's evolution.

Note that I've only looked at some parts of Riak's and CouchDB's
codebase, respectively. Also note that at this point in time, my
knowledge of both Riak's and CouchDB's codebase is still quite limited.


On Sun, 2010-08-22 at 20:37 +0200, Benoit Chesneau wrote:
> On Fri, Aug 20, 2010 at 1:32 PM, Volker Mische <> wrote:
> > +1 for a refactor.
> >
> > GeoCouch duplicates a lot of code. I tried to keep the names in as similar
> > (though meaningful) to the original ones as possible to see where the
> > duplicated code is.
> >
> > I would love to see that everyone who wants a new kind of indexer just need
> > to provide the data structure and all the design document handling, updater
> > (group) handling, list functions etc is done automatically.
> >
> > Cheers,
> >  Volker
> >
> It seems that noone except us is interrestted in that ;) Anyway I'm
> thinking that in case of indexer it would be very useful to have a
> generic way to add some kind of handler allowing any people to plug
> its own stuff to the system indeed.
> Also refactoring would allow us to add comments to the code which
> would help to review code.
> - benoit

View raw message