Skip to main content

[json-processing-spec issues] [JIRA] Updated: (JSON_PROCESSING_SPEC-1) Do not require that all content end up in String or char[]

  • From: "jitu (JIRA)" < >
  • To:
  • Subject: [json-processing-spec issues] [JIRA] Updated: (JSON_PROCESSING_SPEC-1) Do not require that all content end up in String or char[]
  • Date: Wed, 13 Jun 2012 23:16:55 +0000 (GMT+00:00)
  • Auto-submitted: auto-generated


     [ 
http://java.net/jira/browse/JSON_PROCESSING_SPEC-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

jitu updated JSON_PROCESSING_SPEC-1:
------------------------------------


Updating the issue with some related discussion:

http://java.net/projects/json-processing-spec/lists/users/archive/2012-04/message/0
http://java.net/projects/json-processing-spec/lists/users/archive/2012-04/message/2
http://java.net/projects/json-processing-spec/lists/users/archive/2012-04/message/22
http://java.net/projects/json-processing-spec/lists/users/archive/2012-04/message/23
http://java.net/projects/json-processing-spec/lists/users/archive/2012-04/message/25

> Do not require that all content end up in String or char[]
> ----------------------------------------------------------
>
>                 Key: JSON_PROCESSING_SPEC-1
>                 URL: http://java.net/jira/browse/JSON_PROCESSING_SPEC-1
>             Project: json-processing-spec
>          Issue Type: New Feature
>            Reporter: headius
>
> In my work on the JRuby project, it has become painfully obvious that many 
> Java APIs lose performance out of the gate because of the cost of decoding 
> all incoming bytes to char[] before processing them. This also makes it 
> difficult for JVM languages that use a different String representation to 
> use those APIs.
> I propose that the JSON processing API for Java should not impose String or 
> char[] on consumers unnecessarily. In the style of the "spymemcached" 
> library, it should be possible to register a factor that can create strings 
> of other forms directly from the incoming bytes, allowing for parsing and 
> processing JSON without ever decoding. This would make it possible (and may 
> be necessary) to match the performance of C-based libraries, and allows 
> consumers that do not want decoded characters/strings to use the raw bytes 
> directly.
> I will be monitoring this JSR once activity begins and discussions are made 
> public.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://java.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[json-processing-spec issues] [JIRA] Updated: (JSON_PROCESSING_SPEC-1) Do not require that all content end up in String or char[]

jitu (JIRA) 06/13/2012
 
 
Close
loading
Please Confirm
Close