Package mock defines types that are used by different implementations of mock storages.

Handler is the API for Mutable Resources It enables creating, updating, syncing and retrieving resources and their update data.

Constructor.

NewHasherStore creates a hasherStore object, which implements Putter and Getter interfaces.

TODO: Instead of passing the distance function, just pass the address from which distances are calculated to avoid the appearance of a pluggable distance metric and opportunities of bugs associated with providing a function different from the one that is actually used.

NewLDBStoreParams constructs LDBStoreParams with the specified values.

for testing locally.

This constructor uses MemStore and DbStore as components.

NewMemStore is instantiating a MemStore cache.

NewMockDbStore creates a new instance of DbStore with mockStore set to a provided value.

PutChunks adds chunks to localstore It waits for receive on the stored channel It logs but does not fail on delivery error.

When splitting, data is given as a SectionReader, and the key is a hashSize long byte slice (Key), the root hash of the entire content will fill this once processing finishes.

Join reconstructs original content based on a root key.

When splitting, data is given as a SectionReader, and the key is a hashSize long byte slice (Key), the root hash of the entire content will fill this once processing finishes.

http://golang.org/pkg/hash/#Hash.

Chunk also serves as a request object passed to ChunkStores in case it is a retrieval request, Data is nil and Size is 0 Note that Size is not the size of the data chunk, which is Data.Size() but the size of the subtree encoded in the chunk 0 if request, to be supplied by the dpa.

Provides method for validation of content address in chunks Holds the corresponding hasher to create the address.

wrapper of db-s to provide mockable custom local chunk store access to syncer.

LazyChunkReader implements LazySectionReader.

LocalStore is a combination of inmemory db over a disk persisted db implements a Get/Put with fallback (caching) logic using any 2 ChunkStores.

MapChunkStore is a very simple ChunkStore implementation to store chunks in a map in memory.

NetStore implements the ChunkStore interface, this chunk access layer assumed 2 chunk stores local storage eg.

Entry to create a tree node.

ChunkStore interface is implemented by : - MemStore: a memory cache - DbStore: local disk/db store - LocalStore: a combination (sequence of) memStore and dbStore - NetStore: cloud storage abstraction layer - FakeChunkStore: dummy store which doesn't store anything just implements the interface */.

Getter is an interface to retrieve a chunk's data by its reference.

Size, Seek, Read, ReadAt.

Peer is the recorded as Source on the chunk should probably not be here? but network should wrap chunk object.

Putter is responsible to store data and create a reference for it.