| Summary: | Do not include empty entries in RDWP 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: | normal | ||
| Priority: | P3 | CC: | thatnitind |
| Version: | 3.2 | Keywords: | performance |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
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.
|
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).