Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

User Story #870 (new)

Opened 16 years ago

Last modified 10 years ago

Original file service improvements

Reported by: jamoore Owned by: cxallan
Priority: major Milestone: GatherReqs
Component: Services Keywords: IO
Cc: mtbcarroll Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: n.a. Estimated Remaining Time: n.a.


During the various other improvements to the original file service (multiple repositories, in memory representations ,etc.) it may be a good time to think about locking, whether optimistic or pessimistic. Especially for the jobs/scripts, someone may start a threaded uploader, and try to submit a job at the same time. At the moment, it's possible for the submit to request the job script, before the upload is even finished. Some ideas which may or may not already be covered by already planned improvements:

  • add external (i.e. client) access to a read-write-lock
  • have all files be unreadable until marked 'finished' (are they then immutable?)
  • internally we could also use hibernateSession.lock(ofile) to up the optimistic lock number (if we enable it)
  • service method could require a load OriginalFile, since it has an update event to use as a version number

Change History (1)

comment:1 Changed 10 years ago by jamoore

  • Cc mtbcarroll added
  • Keywords IO added
  • Priority changed from minor to major
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.67623 sec.)

We're Hiring!