Github user dholth commented on the pull request:

    https://github.com/apache/couchdb-couch/pull/18#issuecomment-67570751
  
    
    To add _bulk_get support to PouchDB you'd want to copy my version of
    replicate.js into PouchDB itself. It has a couple of extra require()
    calls that PouchDB would not need. Otherwise it is nearly identical to
    the standard replicate.js.
    
    If anything fails we just assume it's not available and switch to using
    GET for the rest of the replication:
    https://github.com/dholth/pouchdb-bulk-get/blob/master/replicate.js#L308
    
    The patch file is outdated but replicate.js is up-to-date as of today.
    
    Having someone else write the Erlang part is fine by me. Here's the
    couchbase _bulk_get which appears to have been recently documented.
    Claims to be multipart/mime only.
    
    
http://developer.couchbase.com/mobile/develop/references/sync-gateway/rest-api/database/post-bulk-get/index.html
    
    I did think my design of allowing *all* GET options in _bulk_get was
    easier to understand/document and it would be nice to be able to pass
    common parameters as GET parameters to the POST _bulk_get request.
    CouchDB has enough inconsistencies in its API as it is.
    
    My CouchDB 2.0 patch attempts to allow all the GET options in _bulk_get
    but I have not really tested it.
    
    On Thu, Dec 18, 2014, at 03:22 PM, Benoit Chesneau wrote:
    > @nolanlawson[1] it also works for Accept: Application/json:
    > 
https://github.com/rcouch/couchdb-couch-httpd/blob/master/src/couch_httpd_bulk_get.erl#L42
    
    > I should document it...
    
    
    > — Reply to this email directly or view it on GitHub[2].
    
    >
    
    
    
    Links:
    
      1. https://github.com/nolanlawson
      2. https://github.com/apache/couchdb-couch/pull/18#issuecomment-67550634


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to