Perform quota checks for writable file stream in the parent process using dedicated task queues
Categories
(Core :: Storage: Bucket File System, task, P3)
Tracking
()
People
(Reporter: janv, Assigned: janv)
References
(Depends on 1 open bug)
Details
Attachments
(10 obsolete files)
Just like SyncAccessHandle, WritableFileStream should perform quota checks in the parent process using dedicated task queues.
See bug 1809043 and bug 1809064.
Assignee | ||
Comment 1•1 year ago
|
||
Parent objects are usually actors as well, but the writable file stream is
special because it will need to do closing asynchronously and potentially have
multiple actors.
Updated•1 year ago
|
Assignee | ||
Comment 2•1 year ago
|
||
Asynchronous closing can't be triggered from the destructor because it needs to
add a strong ref to self.
Assignee | ||
Comment 3•1 year ago
|
||
FileSystemWritableFileStreamResource::Create now returns a MozPromise, but the
creation does nothing on other threads for now.
Assignee | ||
Comment 4•1 year ago
|
||
Active FileSystemWritableFileStreams will prevent FileSystemDataManager from
closing.
Assignee | ||
Comment 5•1 year ago
|
||
The close in the parent is going to be asynchronous as well, so it won't be
guaranteed anymore that the unlocking happens synchronously immediatelly after
receiving the close message.
Assignee | ||
Comment 6•1 year ago
|
||
Assignee | ||
Comment 7•1 year ago
|
||
Assignee | ||
Comment 8•1 year ago
|
||
Assignee | ||
Comment 9•1 year ago
|
||
Assignee | ||
Comment 10•1 year ago
|
||
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Updated•4 months ago
|
Updated•4 months ago
|
Updated•4 months ago
|
Updated•4 months ago
|
Updated•4 months ago
|
Updated•4 months ago
|
Assignee | ||
Updated•4 months ago
|
Description
•