Bug 315111 - Do not include empty entries in RDWP JSON
Summary: Do not include empty entries in RDWP JSON
Status: NEW
Alias: None
Product: JSDT
Classification: WebTools
Component: Debug (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Simon Kaegi CLA
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2010-05-31 12:25 EDT by Michael Rennie CLA
Modified: 2010-06-28 14:48 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-05-31 12:25:49 EDT 
code from HEAD

There are many occurrences when sending requests, receiving responses, etc, that we include extraneous information in our JSON packets.

For example, the scripts request:

{"arguments":{},"command":"scripts","seq":28,"type":"request"}

We are including the "arguments":{} text for no reason. There are many other examples where we include text for no arguments and text for no body.

We should put our JSON on a diet an not include empty entries in the packet(s).
Comment 1 Michael Rennie CLA 2010-05-31 12:37:43 EDT 
another example, the connect response:

{
  "command":"connect",
  "type":"response", 
  "request_seq":27,
  "seq":37,
  "running":true,
  "success":true,
  "body":{}
}

includes the body element for no reason.