#capability-provider #wascc #wasm-file #file #api-bindings

wascc-fs

Blob store capability provider (local file system) for the waSCC runtime

5 releases

0.1.2 Sep 9, 2020
0.1.1 Jul 14, 2020
0.1.0 Jun 4, 2020
0.0.5 May 5, 2020
0.0.4 Apr 27, 2020

#1503 in WebAssembly

Apache-2.0

22KB
526 lines

crates.io  Rust license  documentation

File System Provider

The waSCC File System provider is a capability provider for the wascap:blobstore protocol. This generic protocol can be used to support capability providers like Amazon S3, Azure blob storage, Google blob storage, and more. This crate is an implementation of the protocol that operates on top of a designated root directory and can be used interchangeably with the larger cloud blob providers.

For this provider, the concept of a container is a directory beneath the root (specified via the ROOT configuration variable), while a blob corresponds to a file stored within one of the containers.

Because of the way WebAssembly and the waSCC host work, all wascap:blobstore capability providers must stream files to and from the actor. This allows actors to unblock long enough to allow other messages from other providers to be processed and keeps the WebAssembly module from allocating too much memory.

Dependencies

~4–12MB
~141K SLoC

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy