…he same thread if a Rack app is used (e.g. "devise"). So the Ripple config cannot be stored in the current thread context. I suppose that the goal of setting a different configuration per thread is to use different nodes in the Riak cluster. (I understand that their should be one Riak::Client instance per thread, to send different X-Riak-ClientId headers)
…h race-condition potential).
…not escape squared brackets for example, so Riak complains.
* Let instances do the parsing. * Rename generate_from_map_reduce to load_from_mapreduce. * Automatically detect conflicts and generate siblings more directly. * Don't need to expose conflict/siblings attributes. * Simplify and re-group the spec examples.
- Renamed new_from_map_response to generate_from_map_reduce. - Added load_from_map_reduce instance method.