couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bradford Winfrey <>
Subject Re: Erlang Api for Couchdb
Date Thu, 04 Sep 2008 00:47:56 GMT
I'm not sure if this helps or not, but I just stumbled across this link while looking for some
Varnish/CouchDB information.  maybe some kind of wrapper for erlang
to couchdb in a sane format?  I'm no Erl hacker by any means, so if it's useless please disregard!


----- Original Message ----
From: Damien Katz <>
Sent: Wednesday, September 3, 2008 11:38:10 AM
Subject: Re: Erlang Api for Couchdb

The supported Erlang Apis will simply be to document a core set of the  
internal APIs. These documented apis will, generally speaking, always  
be available and behave the same in future releases of CouchDB.  
Anything not in the API will change freely between revisions and  
shouldn't be used.

But things are still in flux, we just last week change the core json  
term format and I'm anticipating some refactoring changes in the view  
code too. When we get closer to 1.0 we'll start documenting and  
locking down the apis. Until then, you can use the stuff in  
couch_httpd to give you an idea what the apis will be.


On Sep 3, 2008, at 11:06 AM, Michele Sciabarra wrote:

>> Open source, so please scratch your own itch, and all that. But I  
>> will
>> say that we tend to let Damien have first crack at this sort of thing
>> (more core concerns).
> Of course.
>> I have a strong suspicion he's written CouchDB
>> all the way up to version 2.0 in his head, and its just a matter
>> putting it out there.
> So if there is already some idea floating around, maybe could be  
> useful to have some suggestion "from the source" and try to work  
> following it.
>> So go for it if you'd like, but beware that it might only become a
>> suggestion, when all is said and done. ;)
> That's  because I am asking about which ideas are around about the  
> possibile Erlang "native" API for CouchDB.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message