Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315268 - Investigate optimizing Rhino JSON
Summary: Investigate optimizing Rhino JSON
Status: NEW
Alias: None
Product: JSDT
Classification: WebTools
Component: Debug (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Simon Kaegi CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-01 14:05 EDT by Michael Rennie CLA
Modified: 2010-06-01 14:05 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rennie CLA 2010-06-01 14:05:35 EDT 
code from HEAD

The use of JSON for our packet payloads / events / requests / responses was good choice for many reasons, but we should examine closely the strings that we are sending over the wire and the parsing times involved.

In some cases, we have very good concise attribute names like "seq" (the packet sequence attribute), in other cases we have names that are way longer than they need to be - like "constructorFunction" or "prototypeObject".

We should investigate shortening all attribute names to lower the overall packet payload size and to decrease the parsing overhead.