From 25db5d9157b697fb2eecd41fefbd24a92fa8b2b0 Mon Sep 17 00:00:00 2001 From: Richard Stotz Date: Fri, 24 Sep 2021 13:39:16 +0200 Subject: [PATCH 1/3] Add interop warning between SFA and Access Handles --- AccessHandle.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/AccessHandle.md b/AccessHandle.md index 5356d9e..5eecb22 100644 --- a/AccessHandle.md +++ b/AccessHandle.md @@ -60,6 +60,8 @@ System](https://docs.google.com/document/d/121OZpRk7bKSF7qU3kQLqAEUVSNxqREnE98ma [Recommendation for Augmented OPFS](https://docs.google.com/document/d/1g7ZCqZ5NdiU7oqyCpsc2iZ7rRAY1ZXO-9VoG4LfP7fM). +Although this proposal is the successor "in spirit" to Storage Foundation API, the two APIs operate on entirely different sets of files. There exists no way of accessing a file stored through Storage Foundation API using the Origin Private File System, and vice versa. + ## Goals & Use Cases Our goal is to give developers flexibility by providing generic, simple, and @@ -86,6 +88,8 @@ System](https://wicg.github.io/file-system-access/#sandboxed-filesystem), and doesn't currently consider changes to the rest of File System Access API or how files in the host machine are accessed. +This proposal does not consider accessing files stored using Storage Foundation API through OPFS or vice versa. + ## What makes the new surface fast? There are a few design choices that primarily contribute to the performance of From 630f9ad4b413d71e5bb12a75b5bfd88f2e4a06ba Mon Sep 17 00:00:00 2001 From: Richard Stotz Date: Fri, 24 Sep 2021 15:48:55 +0200 Subject: [PATCH 2/3] Update AccessHandle.md Co-authored-by: Thomas Steiner --- AccessHandle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AccessHandle.md b/AccessHandle.md index 5eecb22..0b1ea92 100644 --- a/AccessHandle.md +++ b/AccessHandle.md @@ -60,7 +60,7 @@ System](https://docs.google.com/document/d/121OZpRk7bKSF7qU3kQLqAEUVSNxqREnE98ma [Recommendation for Augmented OPFS](https://docs.google.com/document/d/1g7ZCqZ5NdiU7oqyCpsc2iZ7rRAY1ZXO-9VoG4LfP7fM). -Although this proposal is the successor "in spirit" to Storage Foundation API, the two APIs operate on entirely different sets of files. There exists no way of accessing a file stored through Storage Foundation API using the Origin Private File System, and vice versa. +Although this proposal is the successor "in spirit" to the Storage Foundation API, the two APIs operate on entirely different sets of files. There exists no way of accessing a file stored through the Storage Foundation API using the Origin Private File System, and vice versa. ## Goals & Use Cases From a5e0ada8cf202cf1ff4a416013511478a6721083 Mon Sep 17 00:00:00 2001 From: Richard Stotz Date: Fri, 24 Sep 2021 15:51:01 +0200 Subject: [PATCH 3/3] Fix line breaks --- AccessHandle.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/AccessHandle.md b/AccessHandle.md index 5eecb22..bc4c374 100644 --- a/AccessHandle.md +++ b/AccessHandle.md @@ -60,7 +60,10 @@ System](https://docs.google.com/document/d/121OZpRk7bKSF7qU3kQLqAEUVSNxqREnE98ma [Recommendation for Augmented OPFS](https://docs.google.com/document/d/1g7ZCqZ5NdiU7oqyCpsc2iZ7rRAY1ZXO-9VoG4LfP7fM). -Although this proposal is the successor "in spirit" to Storage Foundation API, the two APIs operate on entirely different sets of files. There exists no way of accessing a file stored through Storage Foundation API using the Origin Private File System, and vice versa. +Although this proposal is the successor "in spirit" to the Storage Foundation +API, the two APIs operate on entirely different sets of files. There exists no +way of accessing a file stored through Storage Foundation API using the Origin +Private File System, and vice versa. ## Goals & Use Cases @@ -88,7 +91,8 @@ System](https://wicg.github.io/file-system-access/#sandboxed-filesystem), and doesn't currently consider changes to the rest of File System Access API or how files in the host machine are accessed. -This proposal does not consider accessing files stored using Storage Foundation API through OPFS or vice versa. +This proposal does not consider accessing files stored using the Storage +Foundation API through OPFS or vice versa. ## What makes the new surface fast?