[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3265: Re-use/keep alive single storage plugin web resource

Tahoe-LAFS trac at tahoe-lafs.org
Tue Nov 19 17:20:16 UTC 2019


#3265: Re-use/keep alive single storage plugin web resource
-------------------------------+---------------------------
 Reporter:  exarkun            |          Owner:
     Type:  enhancement        |         Status:  new
 Priority:  normal             |      Milestone:  undecided
Component:  code-frontend-web  |        Version:  n/a
 Keywords:                     |  Launchpad Bug:
-------------------------------+---------------------------
 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.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3265>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage


More information about the tahoe-lafs-trac-stream mailing list