You should talk to Jin for more clarification on code snippets, but my understanding is that the binary we show IS everything you send for the request. The only parameter you alter is the key you send in binary.
On the second point, we made an explicit decision for 1.8 and 2.0 that we NOT document the binary as the other APIs because it is for people building client libraries, not for people who are using a language-based client library to build a web application. It is for a separate category of developers who are building, for example a Erlang driver or NodeJs driver for Couchbase.
From: Deepkaran Salooja <email@example.com>
Date: Wednesday, May 22, 2013 5:31 AM
To: Karen Zeller <firstname.lastname@example.org>
Cc: Iryna <email@example.com>, Maria McDuff <Maria@couchbase.com>, Iryna Mironava <firstname.lastname@example.org>
Subject: Re: [DOCS Draft Review: Replica Read Binary]
The explanation looks good. Few comments:
- We can have the name/details(e.g. how many arguments) of the API for replica read or some code snippet like we have in case of CAS/append/prepend, which would clarify the usage.
- Also I am a little unclear about keeping this under the section "Chapter8. Developing a Client Library" rather than along with other APIs we provide.