Hi,
On 26 avr. 07, at 10:46, Olivier Grisel wrote:
We will probably soon need to store checksums of file attachments
as part of a customer project. The goal is to be able to quickly
find dupes when importing a bunch of files from a file-system
folder to a nuxeo workspace.
I wondered if it would be relevant to add sha (or md5 ?) checksums
by default in nuxeo, either as a Blob new feature or in a dedicated
field of the file schema computed by a core event listener.
Yes it is, as long as the computation of the checksum is done
asynchronously after an upload. It can definitely add many possible
use case for the platform especially when dealing with large files.
So go on for NXP without forgetting to add the corresponding JIRA
ticket. :-)
Possible usage:
- search / query for documents by checksum provided that the
checksum field is
indexed by the search service;
- invalidation key for the transform service hypothetical cache;
- making it easier to do integrity checks on the client side by
having some
browser plugin on sign the checksum instead of the complete binary;
- additional metadata displayed in the UI so that geeks can check
the integrity of their latest Prison Break^W^W^W Wikipedia iso
before burning it to a DVD;
:-)
Bogdan: what do you think about potential impact of this feature
regarding the planned refactoring on schema for blobs.
Thanks,
EB.
--
Éric Barroca - Ex. VP of Operations - +33 6 21 74 77 64
www.nuxeo.com - Nuxeo: Open Source ECM - www.nuxeo.org
Nuxeo EP 5: extensible, Java EE and standards based ECM Platform !
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
