On Sat, Jan 29, 2011 at 07:40, Carl Worth wrote:

> One idea I've had for this is to change the output (perhaps with a
> command-line option) to avoid emitting the outer array. That is, the
> results would instead be a series of independent JSON objects rather
> than a single JSON object. That should let the application treat things
> quickly by simply calling the JSON parser for each complete
> object.


It might be useful to model this on the Twitter streaming API, which just
delivers a lot of JSON + '\r\n' (large objects straddle http chunks).


> (Though, here, the application would likely want a cheap way to
> know when the input represented a complete object.)
>

Is that necessary? You're definitely going to get a \r\n or an EOF at some
point. :-)

- Jeff