Perhaps arbitrary checksums could be stored as implementation-specific
properties, but fcrepo 4 only uses the SHA-1 in some actionable way in the
core/default fixity checker/etc?
Chris
On 7 Mar, 2013, at 8:48 , Benjamin Armintor <[email protected]> wrote:
> This email concerns Fedora-Futures development, and not work in the FCRepo
> 3.x line.
>
> One of the things that Modeshape does (as do a number of other storage
> services) is key stored bytes of a hash of the content. By default, Modeshape
> uses the SHA1 hash.
>
> Because of this, we are considering doing away with the storage of arbitrary
> checksums for bytestreams, and only using alternative algorithms to verify
> the transfer. So, for example, if you transmit bytes with a MD5 checksum,
> Fedora would use that MD5 to verify the content, but then calculate and store
> only its own checksum (for the sake of argument, SHA1). Queries on the
> datastream "profile" information would return the stored/internal checksum
> (SHA1).
>
> How does everyone feel about this?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Fedora Futures Tech" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/ff-tech?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Fedora-commons-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
