Aeson is used for the very common usecase of short messages that need to be parsed as quickly as possible into a static structure. A lot of things are sacrificed to make this work, such as incremental parsing and good error messages. It works great for web APIs like twitter's.

I didn't even know people used JSON to store millions of integers. It sounds like fun.

  - Clark


On Tue, Dec 4, 2012 at 9:38 AM, Iustin Pop <iustin@google.com> wrote:
On Tue, Dec 04, 2012 at 12:23:19PM -0200, Felipe Almeida Lessa wrote:
> Aeson doesn't have an incremental parser so it'll be
> difficult/impossible to do what you want.  I guess you want an
> event-based JSON parser, such as yajl [1].  I've never used this
> library, though.

Ah, I see. Thanks, I wasn't aware of that library.

So it seems that using either 'aeson' or 'json', we should be prepared
to pay the full cost of input message (string/bytestring) plus the cost
of the converted data structures.

thanks!
iustin

_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe