…tion for when Riak basically returns an empty response body.
Working on adding protobuf support via the protobuf-for-node C++ module next. Finally have enough interest to warrant the level of effort :-)
…to improve socket/connection resuse.
…lobalAgent with our settings.
…list keys and 2i's to only use Riak streaming results API calls behind the scenes.
…decode the content in the event there's the possibility of partial content like a JSON snippet that isn't complete. Now those responses will be parsed out of the multipart response and then individually run through a partial response aggregator which makes sure (at least for JSON) that only full valid JSON blocks will be sent to the decode phase.
adding continuation flag to keylists
…m async and sending them up through the nodiak streaming API.
…ak's result streaming by default behind the scenes, but it may not be exposed in the nodiak API that way for a variety of reasons. For instance if I don't aggregate the results in nodiak from a 2i query then I can't de-dupe it.
… in a x = key || default would cause the key to be set to "" and thus tell Riak to create a key for you rather than use 0.
…k in the case of a 404.
….getHead() to the client backend for use cases where you want to just get the HEAD of an object,
…ed. Now if you pass in an `Array` as input you'll get an `Array` of results as output, unless no results are returned in which case `null` will be sent back. For single scalar input a single `RObject` will be returned.
… results, an Array of results when an Array of keys/RObjects were passed in, and only a single RObject when a single key/RObject was passed in.