You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 14
Next »
Table of Contents
|
Overview
This page is for discussion and description of a proposed "high-level" storage interface for fedora. A draft proposal can be found below. In a nutshell, this proposal aims to remove certain hard-coded storage assumptions in Fedora, and present a storage layer/interface that would allow a place for extensions to Fedora that implement multiplexing, non-blob storage, lock-free updates, etc.
Documents
- Draft proposal (pdf) - Initial proposal for HighlevelStorage layer. Discusses motivation, separation of concerns, and possible use cases.
- Aaron's Presentation - Presented at Feb. 2010 ondon meeting. Summarizes proposal, and introduces a possible configuration of internal modules connected by chaining.
- Asger's Presentation - Presented at Feb. 2010 London meeting. Introduces Writable/Readable store interfaces used for plugging in indexing, caching, etc.
Issues for Discussion
- Interface to DOManager layer
- Datastream versioning
- Return values
- Chaining of modules
Relevant tracker items
Prerequisites and Cleanup
These are issues that represent necessary (or desirable) cleanup of existing code. These issues are general improvements that will make implementing a HighLevelStorage layer easier.
key |
priority |
status |
summary |
assignee |
updated |
|
Issues to revisit
These are issues that may need need to be re-stated in the context of HighLevelStorage, re-implemented using HighLevelStorage concepts, or may be affected in some other way.
key |
priority |
status |
summary |
assignee |
updated |
|
|
#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))