This page will be used to design an asynchronous/pluggable storage feature.

Table of Contents

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

...

The Fedora 4 REST-API MUST A solution must expose a mechanism for clients to request asynchronous content.When the content is prepared, the Fedora 4 client MUST have a means of receiving a notification.When the content is prepared, the Fedora 4 client MUST have some window of time (24h?) to retrieve it from the resulting URL before it expires
The server MAY cache the content response (if appropriate) for some length of time.

The server MAY expose the cached response at the original request endpoint.

A solution must provide the ability to route binary content to different backend stores based on yet-undefined hints