You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (JIRA)" <ji...@apache.org> on 2017/05/02 02:04:14 UTC
[jira] [Closed] (GROOVY-6975) Provide an option to deactivate
escaping in JSON serialization
[ https://issues.apache.org/jira/browse/GROOVY-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul King closed GROOVY-6975.
-----------------------------
> Provide an option to deactivate escaping in JSON serialization
> --------------------------------------------------------------
>
> Key: GROOVY-6975
> URL: https://issues.apache.org/jira/browse/GROOVY-6975
> Project: Groovy
> Issue Type: Improvement
> Components: JSON
> Affects Versions: 2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.3.5
> Reporter: Mathieu Carbou
> Assignee: John Wagenleitner
> Labels: json, serialization
> Fix For: 2.5.0-alpha-1
>
> Attachments: Draft.groovy
>
>
> This is a following of GROOVY-6937 and GROOVY-6852.
> The bug is fixed, but still, we miss a configuration flag in JsonSlurper or somewhere else, or another way to deactivate escaping to have a better serialization output in term of size.
> See the sample attached. Comparing to the JSR 353 Reference Implementation, Groovy output is huge (> 4.8x). In an application requiring utf-8 encoding with a lot of traffic, this is clearly not acceptable.
> As said in GROOVY-6937 and GROOVY-6852, this can be fixed by removing the condition line 370:
> {{c > 126}}
> in:
> {{} else if (c < ' ' || c > 126) {}}
> ;-)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)