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"

Task #10744 (new)

Opened 7 years ago

Last modified 4 years ago

RFE: raw file store empty file semantics

Reported by: mtbcarroll Owned by:
Priority: minor Milestone: Unscheduled
Component: Services Version: n.a.
Keywords: n.a. Cc: jamoore, bpindelski
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

What should be expected from the raw file store API needs to be reviewed.

On the one hand, we probably don't want to create previously-not-existing files just because of a read attempt.

On the other hand, we may want to be able to save empty files without a call to write and to have their checksum correctly set.

Once semantics are agreed, perhaps tests should capture those decisions to prevent regressions.

Change History (3)

comment:1 Changed 7 years ago by jamoore

  • Milestone changed from Unscheduled to OMERO-5

Mark: Blazej and I discussed one possible solution to the hash workflow/handshake which would be to provide a method to pass in the client checksum choice along with the client value on save: rawFileStore.saveWithHash(ChecksumAlgorithm, String clientSideHash) or "setHasherAndHash()" to do things via more remote calls. If we can keep the signature from becoming too complicated, such new methods/arguments on RFS may be a place to handle the empty files.

comment:2 Changed 7 years ago by mtbcarroll

Ah, this might be worth merging with the #10338 discussion then.

comment:3 Changed 4 years ago by jamoore

  • Milestone changed from 5.x to Unscheduled
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.77860 sec.)

We're Hiring!