I'm new to erlang (in fact, the point of CouchDB is I don't have to know erlang). That puts me at a disadvantage in terms of going from configuration to actual processing.
On Sun, May 3, 2009 at 7:35 PM, Jan Lehnardt <[email protected]> wrote: > Hi, > > what exactly are you looking for? CouchDB uses MochiWeb for > all the HTTP grunt work and defines a list of http_*_handlers > that are the various endpoints of the API that then call into > the internal CouchDB API. What bits and pieces do you see > not connected? > > Cheers > Jan > -- > > > On 29 Apr 2009, at 10:25, Howard Lewis Ship wrote: > >> I'm trying to get some understanding of the request handling inside >> couchdb. I've been reading the O'Reilly book, but finding it a bit >> sketchy ... for a CouchDB outsider it needs to work a bit harder to >> connect the dots. Is there a wiki page that describes how the bits and >> pieces fit together? >> >> -- >> Howard M. Lewis Ship >> >> Creator of Apache Tapestry >> Director of Open Source Technology at Formos >> > > -- Howard M. Lewis Ship Creator of Apache Tapestry Director of Open Source Technology at Formos
