Task #4874 (new)
Opened 13 years ago
Last modified 13 years ago
PYR: Add priority queues for requested pyramids — at Initial Version
| Reported by: | jamoore | Owned by: | jmoore |
|---|---|---|---|
| Priority: | minor | Milestone: | OMERO-Beta4.3 |
| Component: | General | Version: | n.a. |
| Keywords: | n.a. | Cc: | jburel, cxallan |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | 1.5d |
| Sprint: | 2011-04-07 (9) |
Description
The background pixel data generated (#4736) will happily (though slowly) work it's way through all of the pixels created. When a user requests a pyramid, a MissingPyramidMessage is raised. This should propagate out to something that will try it's best to generate a pyramid on the fly. If possible, then "retry" can be set to true on the message, permitting a single synchronous call to get the data. If not possible, then a MissingPyramidException needs to be raised which signals that the client will have to retry manually (polling).
See also: #4873
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
