00448: WCS connected field should report dcomm connection status

« 00447 | Issues | 00449 »

Summary: WCS connected field should report dcomm connection status

Created: 2012–10–16 10:55

Status: Released

Category: Request

From: frankie

Version: 2.2

Released_In: 2.3

Description:

the "connected" field in the status XML coming from the WCS should be more useful. Currently it always returns "Yes". This is a request to change it to report the connected state of the client to dcomm servers.

---

Comments

frankie October 16, 2012, at 01:54 PM: This is done. Also, I added the connected field to the dcomm resource as well and updated the xsl to show it.

---

« 00447 | Issues | 00449 »

Associated Commits

| commit | a0889c5a988f9d94384da920d9458a1ac22ef010 link5 | || | Author: | Frank Graffagnino | | Date: | Wed Nov 14 19:10:29 2012 -0600 | | Message: | [@Issue 00398, 00448, 00455: Added in dcomm read-only mode, fixes for dcomm hanging on tcl command, and updated mobile WCS template These issues were loosely interrelated, so they got committed together. For 00398, the read-only mode was added in via the updated plugins. Now, on the command line to the dcomm plugin you can pass in "-read_only" or "-noread_only" to enable and disable read-only mode. There is a new tcl command to query the state, which is why the WCS xml template and mobile pages were updated to reflect this new telemetry. This lead to issue 00448, since when I added in the connected field to the xml, i forgot to update the mobile pages also to include it. So while I added in the read-only mode to both, I also fixed the mobile pages to have the connected field in the general and dcomm status pages. Issue 00455 got committed at the same time because it is also in the dcomm plugins where I applied the fix. Rather than trying to fix the source of the hang, I changed it to where clients always return −1, as it is easier to query this information from the manager directly. Also, it is probably more effecient since it doesn't have to tunnel the information through a tunnel blocking all communication until an answer returns. @] |

Affected Files:

gui/html/lte_edge_root.xsl        |   3 +++
 gui/html/templates/mobile.tmpl    |   6 ++++++
 gui/html/templates/xml_dcomm.tmpl |   1 +
 plugin_Darwin/dsp_dcomm_tc.so     | Bin 229280 -> 229340 bytes
 plugin_Linux_FC3/dsp_dcomm_tc.so  | Bin 68950 -> 69135 bytes
 plugin_Win32/dsp_dcomm_tc.dll     | Bin 1009518 -> 1009554 bytes
 6 files changed, 10 insertions(+)

| commit | 92a93f0ee7b728c2642327908cde8aa98f8a519c link6 | || | Author: | Frankie | | Date: | Tue Oct 16 13:51:05 2012 -0500 | | Message: | [@Issue 00448: Updated connected field to represent dcomm client connection status Updated the connected field on the status page to now reflect the dcomm connection state. Also, added this field to the xml and xsl on the dcomm page. @] |

Affected Files:

gui/html/lte_edge_root.xsl         | 3 +++
 gui/html/templates/xml_dcomm.tmpl  | 9 +++++++++
 gui/html/templates/xml_status.tmpl | 8 ++++++++
 3 files changed, 20 insertions(+)