Ensure results of CNode.listNodes() are cached for a configurable period of time
In v1.3.x, calls to CNode.listObjects() are not cached, which results in thousands of unneeded network calls since the node list changes infrequently. While the convenience method CNode.listNodeIds() uses caching, the API call itself doesn't. Add a NodeListCache object that refreshes its cached copy of the node list after a configurable expiry time has passed. Update CNode to use this cache.
#1 Updated by Chris Jones over 6 years ago
- Subject changed from Ensure results of CNode.listNodes() are cached for a confugurable period of time to Ensure results of CNode.listNodes() are cached for a configurable period of time
- Status changed from In Progress to Rejected
- translation missing: en.field_remaining_hours set to 0.0
After discussion today, we decided that this functionality should be moved to the application level (in particular, Metacat), because of issues with communicating across different CN environments. I'll reject this task for now, and write one up for Metacat and implement it over there.