The APIs listed on this page have the following attributes in common:
- They each provide a means to read and write persistent files with unique ids.
- They were designed with back-end pluggability in mind.
- They are not concerned with directory/folder semantics.
- They are not concerned with versioning semantics, but may allow files to be overwritten.
The Basics
API |
Language |
Target Application(s) |
Known Implementations |
|---|---|---|---|
Java |
Alfresco CMS |
ALF-FS: FileContentStore |
|
Java |
Apache JackRabbit |
||
Java |
Daisy CMS |
||
Java |
DSpace 2 (Unreleased) |
BIT-FS: DSBitStore |
|
Java |
Fedora Repository (2.x to 3.1) |
LLS-FS: GenericFileSystem |
|
Java / C |
Any w/Fixed Content |
||
Java |
Topaz OTM |
||
COM |
MS SQL Server |
Supported Capabilities
- Ids
- Supported ID types?
- Can be store-generated?
- Can be user-provided?
- Content Rewritable?
- 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 - Single impl, supports either local filesystem or SRB
- Eclipse - BlobStore- Assumes local paths and files
- JAF FileDataSource - Assumes local files
- Jakarta Slide ContentStore - Has revision semantics
- OKI Repository OSID - Has container semantics (Assets may contain other assets)
- MediaWiki FileStore - php source?
