...
- They each provide a means to read and write persistent files given a with unique idids.
- They were designed with back-end pluggability in mind.
- They are not concerned with directory/folder semantics.While they may support
- over-writing existing content, they are otherwise They are not concerned with higher-level versioning semantics.
Java
- Apache Jackrabbit - BlobStore
- Daisy (Used with Apache Cocoon) - BlobStore
- DSpace 1 - BitstreamStorageManager
- DSpace 2 - BitStore
- Eclipse - BlobStore
- Fedora Repository - ILowLevelStorage
- JavaBeans Activation Framework - FileDataSource
- MediaWiki - FileStore
- SNIA XAM - Java and C API
- Topaz OTM - BlobStore
Comparison
- , but may allow files to be overwritten.
The Basics
API | API | Type | Used By | Implementations | ||||||
Java | JackRabbit | |||||||||
Java | Cocoon | |||||||||
DSpace 1 BitstreamStorageManager2 BitStore | Java | DSpace | [DSBitStore |
| SRBBitStore | http://wiki.dspace.org/static_files/f/f0/SRBBitStore.java] | Java | DSpace | | |
Java | Fedora | |||||||||
Java | MediaWiki |
| ||||||||
Java / C | * | FileNet? | ||||||||
Java | OTM |
| ||||||||
COM | MS SQL Server |
|
Supported Capabilities
- Ids
- Supported ID types?
- Can be store-generated?
- Can be user-provided?
- Readonly Metadata
- Which are impls expected to provide for reading?
- Settable Metadata
- Which are impls expected to provide for writing?
- Extensible?
- Transactional
- Supported by API?
- Required by impls?
- Two-phase commit?
Other APIs of Interest
- DSpace 1 BitstreamStorageManager - Hardcodes support for either local filesystem or SRB
- JAF FileDataSource - Only works with java.io.FileAssumes local files
- Eclipse - BlobStore- Assumes local paths and files