Content Addressable Storage (CAS) support
From AlfrescoWiki
Contents |
[edit] Project Description
Goal of this project is to provide integration with CAS systems. CAS systems are storage systems based not on location address but on content address. When a CAS is asked to store a file it computes an hash based on its content, it returns it as the address of the stored content and proceed to physically store the content. This address (it's a hash, e.g. d8668fbab44d88f8601e625fd88dee84) is then used as the key to retrieve the content, so when the CAS is presented this address it returns the associated content. As hashing algorithms give a unique association between content and its hashing, this system guarantee:
- Content integrity: if stored content has been altered then there's a mismatch between hash passed as address and hash computed on the fly
- Redundancy avoidance: if CAS is asked to store a content already stored it recognizes that the hash is already present and so doesn't store it again.
[edit] Project Requirements/Objectives
<discuss the project requirements and objectives>
[edit] Initial Project Scope
<outline the initial project scope>
[edit] Discussion of Design/Implementation Approach
For what I understand, anyone feel free to correct me, it's a matter of making an implementation of another content store, ex. we can have a new package org.alfresco.repo.content.cas taking as template the filestore implementation made in org.alfresco.repo.content.filestore.
[edit] Comments
Please use the following format:
Comment Title
<Comment Content>
<Your Name and/or contact info>
Comment from fcorneli@prdbe.jnj.com tel 32-14-603327
We have already implemented a CAS store for Alfresco based on the CASTor product from Caringo. We have donated the code to Alfresco. Ask Paul (H-H) or Mike (Farman)
Frans Cornelissen
Sample Comment 2
This is another sample comment...
Joe Bloggs
