Intent to Experiment: Storage Foundation API
Emanuel Krivoy
Contact emails
five...@chromium.org, rs...@chromium.orgExplainer
https://github.com/fivedots/nativeio-explainer
Specification
NoneAPI spec
YesSummary
Storage Foundation API is a storage API that resembles a very basic filesystem, with direct access to stored data through buffers and offsets. Our goal is to give developers flexibility by providing generic, simple, and performant primitives upon which they can build higher-level components. It's particularly well suited for Wasm-based libraries and applications that want to use custom storage algorithms to fine-tune execution speed and memory usage.
Blink component
Blink>StorageSearch tags
storage, nativeio, performance, low-level, generic, foundationTAG review
https://github.com/w3ctag/design-reviews/issues/566TAG review status
Issues openRisks
Interoperability and Compatibility
This new feature has some potential interoperability risks due to its nature as a novel and low-level API. Currently, there are no web features that expose such a generic interface and that focus on WebAssembly ports as one of it's main consumers.
Gecko: No signal (https://github.com/mozilla/standards-positions/issues/481)
WebKit: No signal (https://lists.webkit.org/pipermail/webkit-dev/2021-February/031687.html)
Web developers: No signals
Goals for experimentation
In general, we would like to validate the whole surface of our API against developer expectations and more diverse use cases. In particular, we are interested in confirming that we provide the required performance to allow new uses, and to shed light on developer preference between a synchronous and asynchronous surface.
Reason this experiment is being extended
Ongoing technical constraints
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
YesIs this feature fully tested by web-platform-tests?
YesTracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=914488Launch bug
https://bugs.chromium.org/p/chromium/issues/detail?id=1143306Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5670244905385984Links to previous Intent discussions
Intent to prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/gh0gTHO18YQ
Masataka Yakura
Contact emails
five...@chromium.org, rs...@chromium.orgExplainer
https://github.com/fivedots/nativeio-explainerSpecification
NoneAPI spec
YesSummary
Storage Foundation API is a storage API that resembles a very basic filesystem, with direct access to stored data through buffers and offsets. Our goal is to give developers flexibility by providing generic, simple, and performant primitives upon which they can build higher-level components. It's particularly well suited for Wasm-based libraries and applications that want to use custom storage algorithms to fine-tune execution speed and memory usage.
Blink component
Blink>StorageSearch tags
storage, nativeio, performance, low-level, generic, foundationTAG review
https://github.com/w3ctag/design-reviews/issues/566TAG review status
Issues openRisks
Interoperability and Compatibility
This new feature has some potential interoperability risks due to its nature as a novel and low-level API. Currently, there are no web features that expose such a generic interface and that focus on WebAssembly ports as one of it's main consumers.
Gecko: No signal (https://github.com/mozilla/standards-positions/issues/481)
WebKit: No signal (https://lists.webkit.org/pipermail/webkit-dev/2021-February/031687.html)
https://github.com/mozilla/standards-positions/issues/481#issuecomment-774919680
Emanuel Krivoy
Risks
Interoperability and Compatibility
This new feature has some potential interoperability risks due to its nature as a novel and low-level API. Currently, there are no web features that expose such a generic interface and that focus on WebAssembly ports as one of it's main consumers.
WebKit: Negative (https://lists.webkit.org/pipermail/webkit-dev/2021-February/031687.html) No opposition to offering efficient access to files, strongly opposed to minting a new API instead of augmenting an existing one.
Web developers: No signals
Yoav Weiss
I'm sorry, I had updated Chrome Status before sending the email, but did not update the email draft. Here is what the risk section should have said:Risks
Interoperability and Compatibility
This new feature has some potential interoperability risks due to its nature as a novel and low-level API.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHExSGLF%2BfC73GMtEiGL%3Donc0D968EhO%2B4Nn5crCi%3DakqG0MMQ%40mail.gmail.com.
Emanuel Krivoy
I agree, the question of our relationship with other storage APIs is at the top of our list. We are still in active conversation with the storage team, although we’ve fallen a bit behind on this topic because of shifting deadlines. Before these shifts, we were discussing the ways that we could cover the use cases of the Origin Private Filesystem and Storage Foundation API under one surface, and what the costs in performance and simplicity would be.
This origin trial will help us in that discussion, since getting a broader understanding of how developers/partners use our API will inform the solutions we explore.