Re: [dsdp-tcf-dev] RE: [Bug 301578] Orbit should offer JSON tools

[Doug Schaefer <cdtdoug@xxxxxxxxx>]

No, that sounds fine. The key is the handling of binary data which is a must for the types of things we need to do with TCF. Although as more and more things use the binary data we start to lose some of the other benefits you list. A pure binary protocol might be better suited but they are more effort to manage.

I was really just making the point that it isn't really the "official" JSON, so we can't use the version in Orbit. And as Michael mentioned, json is simple enough people don't think twice of doing their own implementation to meet their needs.

Cheers,
Doug.

On Wed, Feb 3, 2010 at 11:10 AM, Burton, Felix <Felix.Burton@xxxxxxxxxxxxx> wrote:

Hi Doug,

 

We use JSON because it is

 

1. Small and simple: The definition on json.org fits on one or two printed pages
2. Human readable
3. Compact: There is very few characters of overhead
4. Typed: Each value has a well defined type
5. Simple to parse and generate
6. Extensible

 

IIRC we have two extensions, 1) to represent a null error code as a single byte, 2) to represent binary data.  The second one is optional.

 

I am not aware of a better format for our needed.  Do you have something in mind?

 

Thanks,

Felix

 

From: dsdp-tcf-dev-bounces@xxxxxxxxxxx [mailto:dsdp-tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: Tuesday, February 02, 2010 10:16 PM
To: DSDP TCF dev list
Subject: Re: [dsdp-tcf-dev] RE: [Bug 301578] Orbit should offer JSON tools

 

All of those questions beg the question, why are we using JSON for this if it doesn't support our requirements. Or, in other words, despite being called JSON, are we really using JSON. We should be clear on what we're doing here.

Doug.

On Tue, Feb 2, 2010 at 10:00 PM, Tarassov, Eugene <eugene.tarassov@xxxxxxxxxxxxx> wrote:

Hi Martin,

To consider alternative JSON implementation we would need a proof that:
1. It is faster then current implementation - JSON is part of
time-critical path in TCF;
2. It has no dependencies beyond standard Java;
3. It can be extended to support unformatted binary data blocs - aka TCF
Zero Copy protocol.

Regards,
Eugene

-----Original Message-----
From: Oberhuber, Martin
Sent: Tuesday, February 02, 2010 11:35 AM
To: Tarassov, Eugene
Cc: DSDP TCF dev list
Subject: FW: [Bug 301578] Orbit should offer JSON tools

Hi Eugene and all TCF committers,

Would it be beneficial for TCF Java side to leverage JSON Utilities from
the external lib (see below) rather than Cooking our own JSON?

Thanks,
Martin

-----Original Message-----
From: bugzilla-daemon@xxxxxxxxxxx [mailto:bugzilla-daemon@xxxxxxxxxxx]
Sent: Tuesday, February 02, 2010 8:11 PM
To: Oberhuber, Martin
Subject: [Bug 301578] Orbit should offer JSON tools


https://bugs.eclipse.org/bugs/show_bug.cgi?id=301578
Product/Component: Orbit / bundles

--- Comment #1 from Austin Riddle <austin.riddle@xxxxxxxx> 2010-02-02
14:11:09 EST --- Sorry to be terse in my last post.  The JSON code
approved for use in CQ3603 would be useful for reference in a RAP
contribution that provides Google Visualizations.  Currently the
contribution contains the code in its own bundles, which is less than
ideal.

Thanks.

--
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: ------- You are watching
the assignee of the bug.
_______________________________________________
dsdp-tcf-dev mailing list
dsdp-tcf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-tcf-dev

 

_______________________________________________
dsdp-tcf-dev mailing list
dsdp-tcf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-tcf-dev