Task #982 (assigned)
Opened 16 years ago
Last modified 15 years ago
Develop our own ActiveServant container with eviction
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | major | Milestone: | GatherReqs |
| Component: | Services | Version: | 3.0-M1 |
| Keywords: | blitz, servants, evictor, freeze, complexity, abstraction | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
#883 shows that the servant logic in ServiceFactoryI has gotten too complicated and should be abstracted, especially as we add more types (Processors, Process, Callbacks, etc.) which need to be managed. Look into using FreezeEvictor?, but this must work properly with OmeroSessions.
Change History (3)
comment:1 Changed 16 years ago by jmoore
- Status changed from new to assigned
comment:2 Changed 16 years ago by jmoore
Iniitally implemented as "ServantHolder" in r2708 and updated in r2722 under the OmeroThrottling umbrella.
comment:3 Changed 15 years ago by jmoore
- Milestone changed from OMERO-Beta4 to GatherReqs
Not for 4.0. Moving to GatherReqs?, until it's clearer what's needed.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
r2397 shows an example of issues (i.e. stupid mistakes) when servant mgmt is not abstracted away.