Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CADA=EV9KizJ0duYWkdnTf11KNYAh8gyT9XrCzVHv95+HGRbeWw@mail.gmail.com>
References: 
 <CADA=EV9KizJ0duYWkdnTf11KNYAh8gyT9XrCzVHv95+HGRbeWw@mail.gmail.com>
Date: Fri, 8 Jun 2012 12:43:06 -0400
Message-ID: 
 <CALpjNym++wpudqaD-thV=HZrBdOJRkrQBbv1g=X04bydUYDRDw@mail.gmail.com>
Subject: Re: Node.js client for CouchDB
From: Sam Bisbee <sam@sbisbee.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=e89a8f13ec7ad1c66f04c1f8b1b4

--e89a8f13ec7ad1c66f04c1f8b1b4
Content-Type: text/plain; charset=UTF-8

Nano is the most popular, cradle seems to be less popular, and
saggingcouch.com gives you JS in browser and node with a mirrored API in
PHP (I wrote sag so am biased).

Or just use a straight HTTP lib like Mikeal's request.

Cheers,

--
Sam Bisbee
Sent from my phone so please excuse brevity and typos.
On Jun 8, 2012 9:21 AM, "Pulkit Singhal" <pulkitsinghal@gmail.com> wrote:

> Hello Folks,
>
> What are some good node.js clients for communicating with CouchDB?
>
> If you are having trouble understanding why I would even want one then just
> imagine that the app will not sit as a design document inside CouchDB but
> rather be elsewhere and simply talking to CouchDB via the node.js client.
> Or imagine that I'm doing TDD test driven development where I want to flesh
> out the user-stories and workflow as nothing more than 10 or 12 calls to
> CouchDB. Now I COULD do this via curl but parsing the output from previous
> JSON responses in a big test driven workflow is not exactly a joyous or
> successful task for me to accomplish.
>
> So far I've only found nano (https://github.com/dscape/nano) and I find
> myself wondering why someone hasn't simply taken the javascript code that
> runs Futon and dropped it into a node.js module? Has something like this
> been done? Because that would (in my imaginary world) provide a full blown
> client for use within node.js :)
>

--e89a8f13ec7ad1c66f04c1f8b1b4--