ACCESS-CONTROL-ALLOW-ORIGN problem would seem to be something that should be mentioned
Having spent the better part of a day that I didn't have to waste trying to get couchdb to work with jQuery, this post may be a bit distempered. (If I'm wrong, I'll be more than happy to admit it.)
See my previous post about jquery.couch.js not working with current versions of jQuery.
Now, I find out that -- thanks to Chrome's detailed messages -- that I can't access couchdb from a different domain and that seems to include a different port on the same domain.
I have couchdb installed and apparently working on my laptop on port 5984, the default. I access it with http://localhost:5984/_utils.
My application is running on IIS from http://localhost/
Trying to do $.ajax() requests from my app consistently fails due to the access control issue (which doesn't show up in Firebug, btw, but does show up in Chrome's developer tools).
According to what I googled, there is no way to configure couchdb to serve up to other addresses.
My first decision was that couchdb was pretty much useless if not available from other addresses though that was a bit unfair because the problem relates to something intrinsic to web browsers and making http requests from them -- the need to be secure against cross-domain scripts.
But, having said that, it seems to me that this issue should be prominently highlighted in the documentation. I suppose many people familiar with Ajax driven apps will be familiar with it, but those of us who are somewhat new to the party would be helped by pointing out that in order to use couchdb across domains you'll likely need some kind of server-side code to make it work.
Not knowing that one quirk can, I can attest, waste a tremendous amount of time.