basho/riak-ruby-client — pull request #60 by seancribbs (2012-10-15 20:49:14+00:00)
Title: Refactor siblings behavior

The goal here is to proactively prevent saving back a siblings response as a normal object with the `multipart/mixed` content type. This also clarifies and simplifies the internal model of siblings. See also #52.

Changes:

(Also includes some minor whitespace/bug-fixes).

* `Riak::Conflict` will be raised when attempting to save an `Riak::RObject` with siblings.
* Siblings are represented as `Riak::RContent` objects rather than nested, interlinked `Riak::RObject` instances.
* Most original accessors will work if the `Riak::RObject` is not in conflict, delegating to the singular `Riak::RContent` behind it. If in conflict, `Riak::Conflict` will be raised.