search

WICG / storage-foundation-api-explainer

Explainer showcasing a new web storage API, NativeIO
Apache License 2.0
63 stars 8 forks source link

Update NativeIO name to Foundation Storage API #14

Closed fivedots closed 3 years ago

fivedots commented 3 years ago

This PR updates the README and security questionnaire with our new name. The examples and IDL have not been updated, to avoid confusion until the change lands in Chrome.

I'll rename the repos and create redirects after this PR is merged.

asutherland commented 3 years ago

Is it possible to link to the discussion that led to the new name (if an online discussion) or provide a synopsis (if an offline discussion)?

kaizhu256 commented 3 years ago

yea, the new name is confusing. wasn't the whole point to provide/virtualize"native", system-level file-api's for emscripten/wasm-sqlite (something wicg's filesystem-api could not do)?

fivedots commented 3 years ago

Hello @asutherland, @kaizhu256, thanks for reaching out,

The reason the name was changed is two-fold:

After a long-running internal discussion, we settled on the new name because it nicely conveys the idea that this is a low-level API, and that one of its main use cases is to act as the basis for more complex storage semantics. Of course, we are open to feedback and change, especially if there are strong reasons on why we shouldn’t go for Storage Foundation API.

kaizhu256 commented 3 years ago

are there use-cases outside of database/streaming-media? if not how about something along lines of "dbfs" or "streamfs"?

"foundation-storage-api" doesn't help in educating ppl why wicg-filesystem-access-api is inappropriate for above scenarios (and reason for this proposal).

asutherland commented 3 years ago

Thank you for the context and links! The new name seems to nicely address both concerns!