id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	launchpad_bug
3265	Re-use/keep alive single storage plugin web resource	exarkun		"The storage plugin web feature currently asks the storage plugin for its web resource every single time.  This generally means there is one web resource per web request.  This means the web resource can't have any persistent state unless it finds somewhere else to keep it.

It would be more convenient if the web resource could have persistent state on itself which was guaranteed to live as long as the node itself lives (which is approximately as long as the Python process lives).

An alternative to this would be for the plugin itself to keep the web resource alive and return it for repeated calls to `get_client_resource`.  This is problematic because the node's whole configuration is a parameter to this method.  The plugin would need to implement caching which correctly respects the node configuration which is non-trivial.
"	enhancement	closed	normal	undecided	code-frontend-web	n/a	fixed	review-needed