groovy-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wilson MacGyver <wmacgy...@gmail.com>
Subject Re: Questions about JSonSlurper
Date Fri, 05 Jun 2015 15:40:49 GMT
JsonSlurper will deal with it just fine. We do this regularly with 3mb-5mb
gzipped json. In fact we gunzip it in memory and processing via groovy in
place

On Sun, May 31, 2015 at 8:14 AM Rakesh Patel <patel.rakesh@gmail.com> wrote:

> I have a 2.5MB zipped payload. I was hoping I could get the benefit of
> Boon by using JSonSlurper instead of Jackson but then I have this use case
> for streaming the data.
>
> On Sun, 31 May 2015 at 13:02 Guillaume Laforge <glaforge@gmail.com> wrote:
>
>> How big is your JSON payload?
>> Our parsers are quite efficient.
>>
>> JsonSlurper is cheap to build, and you should build one per thread.
>>
>> There's also the JsonLexer that could be used, if you want to do it in a
>> token streaming fashion.
>>
>> Guillaume
>>
>>
>> 2015-05-31 13:28 GMT+02:00 Rakesh Patel <patel.rakesh@gmail.com>:
>>
>>> Does it support token streaming or do I have to use something like
>>> Jackson? I have a very big Json payload to process.
>>>
>>> Is JsonSlurper thread safe? Or do I need to new one up each time per
>>> thread?
>>>
>>> Thanks
>>>
>>
>>
>>
>> --
>> Guillaume Laforge
>> Groovy Project Manager
>> Product Ninja & Advocate at Restlet <http://restlet.com>
>>
>> Blog: http://glaforge.appspot.com/
>> Social: @glaforge <http://twitter.com/glaforge> / Google+
>> <https://plus.google.com/u/0/114130972232398734985/posts>
>>
>

Mime
View raw message