If the user requests to have the body parsed, the body is piped through the parsers (JSON or XML). Design-wise, it's up to those parsers what type of chunks would be emitted -- at the moment, I kept the behavior close to what it already was. But I can imagine adding an RSS parser that would make resp.body an array of RSS items, for example.

Stream-based parsers such as JSONStream allow you to provide a so-called selector. 

```javascript
var stream = needle.get(...).pipe(new JSONStream('rows.*'})); 
```
Which would only emit objects from the 'rows' array. In other words: this adds a lot of flexibility.

Having said that, I personally am against integrating too much of this logic into the main Needle code, and make this more plugin-based. When using streams, there is no need at all to have this dependency in Needle itself, since it's so easy to pipe it though a stream parser.