#664: Review of AccessHandles for the Origin Private File System

Visit on Github.

Opened Aug 5, 2021

Ya ya yawm TAG!

I'm requesting a TAG review of AccessHandles for the Origin Private File System.

We propose augmenting the Origin Private File System (OPFS) with a new surface that brings very performant access to data. This new surface differs from existing ones by offering in-place and exclusive write access to a file’s content. This change, along with the ability to consistently read unflushed modifications and the availability of a synchronous variant on dedicated workers, significantly improves performance and unblocks new use cases for the File System Access API.

Further details:

You should also know that...

A previous iteration of an API to cover these use cases has already gone through an early TAG review: #566. This new proposal is a response to feedback that NativeIO seemed to duplicate existing functionality and should be integrated into the File System Access API.

We'd prefer the TAG provide feedback as (please delete all but the desired option):

💬 leave review feedback as a comment in this issue and @-notify @fivedots and @rstz

Discussions

Discussed Aug 16, 2021 (See Github)

Ken/Sangwhan: We looked at it during our breakout today, the proposal and problem statement looks good to us. We'll discuss this further in the plenary and see if we can close this.

Comment by @cynthia Aug 17, 2021 (See Github)

@kenchris and I looked at it during our breakout today, the proposal and problem statement looks good to us. We'll discuss this further in the plenary and see if we can close this. Thanks!

Comment by @fivedots Aug 27, 2021 (See Github)

Thank you for the update, @cynthia! Just for our planning, when will the next plenary be?

Comment by @cynthia Aug 28, 2021 (See Github)

We have one every week, but I missed the last one. There is one this week so I'll try to put it into the agenda.

Discussed Sep 1, 2021 (See Github)

closed

Comment by @cynthia Sep 14, 2021 (See Github)

We discussed this during our VF2F, and group consensus was that this is good to go. Apologies for the delay, and thank you for bringing this to our attention!