add TOC and Docker REST example
minor deploy image fix
Merge pull request #181 from tschottdorf/rdme

add REST example and TOC to readme
fix the 7-bytes binary decoding error
Merge pull request #184 from joezxy/master

fix the 7-bytes binary decoding error
Move all cases of direct "engine" access to inline-MVCC.

This is a necessary step towards ranges which will contain time series
data, which requires merging. Efficient merging cannot be done using
our multi-row MVCC model. This change provides an inline value in the
MVCCMetadata which is used instead of a versioned value if the timestamp
is specified as zero. Inline values are replaced on successive puts and
are cleared on deletes.

The inlined values can be accessed just like versioned values, and all
MVCC operations work, modulo differences in how timestamps are interpreted.
Once a value has been written as inline, it may not be overwritten using
a timestamp for version values. Inlined values support merge.

Currently, the stats are inaccurately kept for merge, though the next
change will do benchmarks to ascertain the cost of keeping accurate
stats.
Merge pull request #185 from cockroachdb/spencerkimball/inline-mvcc

Move all cases of direct "engine" access to inline-MVCC.
add proto.Combinable interface

Combinable is implemented by responses whose requests may access multiple ranges,
such as {Scan,DeleteRange}Response and allows multiple responses to be merged
into a single one transparently.
allow multi-range Scan and DeleteRange

adapted the distributed sender to split such requests up
and adress them to the individual ranges.
The Combinable interface is used to create a single response
from those parts which is returned with the client.Call.
test multi-range Scan and DeleteRange
address Kathy's comments
address @spencerkimball's feedback
refactor server_test to use TestServer singleton
assert err on range-spanning GET