Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 315268

Summary:	Investigate optimizing Rhino JSON
Product:	[WebTools] JSDT	Reporter:	Michael Rennie <Michael_Rennie>
Component:	Debug	Assignee:	Project Inbox <jsdt.debug-inbox>
Status:	NEW ---	QA Contact:	Simon Kaegi <simon_kaegi>
Severity:	enhancement
Priority:	P3	CC:	thatnitind
Version:	3.2
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Michael Rennie

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.