Versions Compared

Old Version 70

changes.mady.by.user Andrew Woods

Saved on

compared with

New Version 71

changes.mady.by.user Danny Bernstein

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Goals

  1. Preservation storage
  2. Simplicity
  3. Performance

Implementation Plan

  1. Remove Modeshape
  2. Create 2-3 APIs to allow plugging in new backends
  3. Implement OCFL 

Major CRUD-Related Interfaces

Use Case:  Simple OCFL - based implementation

OCFL Client with persistent database as authoritative metadata source

 

Use Case: Horizontally-Scaled Fedora Instances Running against a single OCFL

 

Use Case:  Fast reads and writes with OCFL 



WORK IN PROGRESS:  Fedora Session to OCFL Session Management - try to understand how Fedora Transactions (managed by FedoraSession) would map to a set of OCFL Sessions.

The problem:  A Fedora transaction may span multiple HTTP Requests.   Assuming that we do not want to commit anything to OCFL until the Fedora Transaction is committed, how do we maintain the state of open OCFL Sessions

across requests.  How also do we ensure that two requests using the same transaction ID do not stomp on each other?   It seems that this is only becomes a problem if we want to support autoscaling of Fedora instances.