00486: implement WCS caching to handle back-to-back requests

« 00485 | Issues | 00487 »

Summary: implement WCS caching to handle back-to-back requests

Created: 2013–03–13 12:00

Status: Released

Category: Request

From: frankie

Version: 2.3

Released_In: 2.4

Description:

Some of the resources that the WCS serves up, such as the node list, rarely change, if ever. This is a request to be able to provide additional arguments to the WCS template callbacks so that their responses can be cached for some amount of time. That way requests for the same response happening within that window will get a cached response without searching for the appropriate callback or building a new response.

---

Comments

frankie March 13, 2013, at 12:05 PM: This has been implemented. New arguments to the wcs_callback command can be seen in web_commanding_server.tcl. Some callbacks that have data that rarely changes have their expiration set to 10 seconds, while some others that change slowly (such as status), update every 3 seconds. Others which can change at any time have no expiration set.

---

« 00485 | Issues | 00487 »

Associated Commits

| commit | dd060ef950d3158e5b50b375da3412951fec35a3 link5 | || | Author: | Frank Graffagnino | | Date: | Wed Mar 13 12:16:57 2013 -0500 | | Message: | [@Issue 00486: Implemented WCS caching Now, if a templated resource is requested multiple times it can be returned from a cache depending on the expiration time set for each resource. Also, found some missing resources in the xml_resources.tmpl file so quickly added those in. @] |

Affected Files:

gui/html/templates/xml_resources.tmpl |   4 ±
 gui/web_commanding_server.tcl         | 141 +++++++++++++++++++++++++±-------
 2 files changed, 111 insertions(+), 34 deletions(-)