Task #2672 (new)
Opened 14 years ago
Last modified 14 years ago
Develop ram and/or db queue structure for delete
Reported by: | jamoore | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | Unscheduled |
Component: | Services | Version: | n.a. |
Keywords: | n.a. | Cc: | |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | 2.0d |
Sprint: | n.a. |
Description
The state of the delete service will have to reside somewhere. Options are:
- mark the top-level (the submitted object) in the db
- use a concurrent data structure in memory (lost of restart)
- persist to Freeze or some similar on-disk location
Change History (4)
comment:1 Changed 14 years ago by jmoore
- Sprint set to 2010-08-12 (14)
comment:2 Changed 14 years ago by jburel
- Sprint changed from 2010-08-12 (14) to 2010-08-26 (15)
comment:3 Changed 14 years ago by jmoore
- Sprint 2010-08-26 (15) deleted
comment:4 Changed 14 years ago by jmoore
- Milestone changed from OMERO-Beta4.2.1 to Unscheduled
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Based on discussion Sep.2 moving this to unscheduled.