Task #10535 (closed)
Opened 6 years ago
Closed 6 years ago
Server-side caching of file resources
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | critical | Milestone: | 5.0.0-beta1 |
| Component: | Services | Version: | n.a. |
| Keywords: | fs | Cc: | web-team@…, fs@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | FS Demo 3 |
Description
As a different strategy for handling the issues presented in #10178, a server-side cache for filehandles, BF readers, etc. should be put in place. In the short-term, this should make calling renderingEnginePrx.setId() nearly costless if the said file is still in the cache.
Longer-term, it would be nice to turn this caching facility into stateless, file-access so that OMERO.web doesn't have to maintain any services or worry about closing them, etc.
Change History (1)
comment:1 Changed 6 years ago by jamoore
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
BF work can likely be backported to dev_4_4 if desired.