This page will be used to design an asynchronous/pluggable storage feature.
Guiding Principles
- Any Fedora4 feature should be available through an API which is an implementation of LDP or an optional extension (ideally an existing standard)
- Fedora4 features should favor existing tools over custom code
- Fedora4 features should establish integration patterns where an implementation is not a part of the core code
Use Cases
Use Cases - Asynchronous and Pluggable Storage
Use Case Evaluation - F4 Asynchronous Storage
Actions
...
Proposed Requirements
- A solution must expose a mechanism for clients to request asynchronous content
- A solution must provide the ability to route binary content to different backend stores based on yet-undefined hints
Role Commitments
Development
...
Stakeholder
...
