Skip to main content

[json-processing-spec users] Re: JSON_PROCESSING_SPEC-1 : Do not require that all content end up in String or char[]

  • From: Jitendra Kotamraju < >
  • To:
  • Subject: [json-processing-spec users] Re: JSON_PROCESSING_SPEC-1 : Do not require that all content end up in String or char[]
  • Date: Fri, 30 Nov 2012 15:44:50 -0800

On 11/29/2012 08:47 PM, Tatu Saloranta wrote:
On Thu, Nov 29, 2012 at 1:28 PM, Jitendra Kotamraju
< >
 wrote:
On 11/26/2012 02:23 PM, Jitendra Kotamraju wrote:
Can we also discuss this one:

http://java.net/jira/browse/JSON_PROCESSING_SPEC-1
I haven't seen much discussion on this. I would like to close this one with
no action. I don't see parsers are operating at byte level so there is no
point in exposing the byte array instead of String. If someone really wants
to do this, they could write a custom provider that extends JsonParser and
provide a custom JsonString that exposes a byte array. So, I don't think it
needs to be in the API.
I see byte-level access a rather specialized feature, and as not
making sense for this version.
And although it would be possible to return CharSequence
(implementations of which could then implement additional byte[]-based
interfaces), it just does not seem all that useful to me. Especially
considering that we have deferred other simpler performance-related
possible additions.
Let me send PR draft next week for review. I want all of you spend some time
on that and see if there are any issues.

We can consider *some* of the deferred ones based on the schedule, priority
and PR feedback.  We don't have much time before proposed final draft.

Jitu

-+ Tatu +-



[json-processing-spec users] JSON_PROCESSING_SPEC-1 : Do not require that all content end up in String or char[]

Jitendra Kotamraju 11/26/2012

[json-processing-spec users] Re: JSON_PROCESSING_SPEC-1 : Do not require that all content end up in String or char[]

Jitendra Kotamraju 11/29/2012

[json-processing-spec users] Re: JSON_PROCESSING_SPEC-1 : Do not require that all content end up in String or char[]

Tatu Saloranta 11/30/2012

[json-processing-spec users] Re: JSON_PROCESSING_SPEC-1 : Do not require that all content end up in String or char[]

Eugen Cepoi 11/30/2012

[json-processing-spec users] Re: JSON_PROCESSING_SPEC-1 : Do not require that all content end up in String or char[]

Jitendra Kotamraju 11/30/2012

[json-processing-spec users] Re: JSON_PROCESSING_SPEC-1 : Do not require that all content end up in String or char[]

Jitendra Kotamraju 11/30/2012
 
 
Close
loading
Please Confirm
Close