Reduce StoreManager API

[michielbdejong]

Also addresses #129, #133, #126, #124.

[michielbdejong]

Did a lot of refactoring, need to get unit tests in shape again now.

[michielbdejong]

In the previous design, ResourceData could travel all the way from a Blob to the HttpResponder. Now, we should have different things in different layers:

5. pod-server

4. wac-ldp

• HttpResponder needs a Representation, which is very similar to ResourceDataLdpNr but let's keep them separate in case we want to, for instance, change how/where ETags are generated

  3. StoreManager

• getRepresentation/setRepresentation
• load/save
• patch
• statementsMatching, subjectsMatching, predicatesMatching, objectsMatching
• addQuads, removeQuads

  2. QuadAndBlobStore

• read(url) -> ResourceData (-LdpBc | -Missing | -LdpRs | -LdpNc)
• write(url, ResourceDataLdpRs | ResourceDataLdpNc)
• delete

  1. BlobTree

• getContainer
  • exists
  • delete
  • getMembers
• getBlob
  • exists
  • delete
  • getData() => Array (in v2 format, that's [contentType, etag])
  • setData(Array) (in v2 format, that's [contentType, etag])
  • getBody() => ReadableStream
  • setBody(ReadableStream)

[michielbdejong]

interface Blob extends Node {
  getData (): Promise<Array<Buffer>>
  setData (data: Array<Buffer>): Promise<void>
  getBodyVersion (etag: string): Promise<ReadableStream>
  setBodyVersion (etag: string, data: ReadableStream): Promise<void>
  deleteBodyVersion (etag: string): Promise<void>
}

[michielbdejong]

Three important interfaces:

• wac+ldp level: WacLdp
• rdf level: StoreManager
• persistence level: BufferTree + ResourceNode

[michielbdejong]

Cancelled in favour of Operation Treasure Trove.