You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Web apps may create temporary files that are meant to be deleted when they are implicitly closed. That is, when a tab closes, these temporary files should not be persisted.
Perhaps the behavior should be similar to the posix unlink function.
The text was updated successfully, but these errors were encountered:
I think support for temporary files in some manner might make sense, yes (see also my reply to #340). Not sure that allowing removing of a file while it is open/locked is the way I'd approach this. I'd rather just not have the file exists in a directory to begin with, which seems like it should address the same use case?
And storage buckets with a session scoped lifetime might also help here (although we'd have to define what session scoped actually means, i.e. does it delete data on tab closure, or on browser closure, or something else...)
Web apps may create temporary files that are meant to be deleted when they are implicitly closed. That is, when a tab closes, these temporary files should not be persisted.
Perhaps the behavior should be similar to the posix unlink function.
The text was updated successfully, but these errors were encountered: