Task #1706 (new)
Opened 14 years ago
Last modified 14 years ago
Server should raise specific exception on conflicting deletes
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | major | Milestone: | Unscheduled |
| Component: | API | Version: | 4.1 |
| Keywords: | n.a. | Cc: | jburel |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Unless we serialize all deletes (or other specific actions), delete issues like in #1654 are most likely best handled by using an OptimisticLockException (or a subclass thereof) to inform clients that two deletes happened at the same time.
Does there need to be more information in the exception so that a client can properly display to the user "oh, you just tried to delete that!" ?
See #1654
Change History (2)
comment:1 Changed 14 years ago by jmoore
- Type changed from User Story to Task
comment:2 Changed 14 years ago by jmoore
- Milestone changed from OMERO-Beta4.2 to Unscheduled
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Jean-Marie, I'm moving this to unscheduled. If you think you have time to make use of it, we can add it back in.