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
I would like to implement filesystem access in my project, but it requires some thought.
We could reproduce the classic open/read/write API, but how should we expose
"mount points" for applications?
Ideally, I would like to provide FS access to the local disk, but also have a transparent
access to file storage systems like S3.
The text was updated successfully, but these errors were encountered:
I think we can take the "everything is a URL" concept from Redox and base all resource locations (e.g. Local paths, remote addresses, S3 storage keys) on URLs with different protocol schemes.
In this way, any resource representable as a URL can be assigned a Resource Identifier unique to the current application at the time of being opened, and things like Metadata or Stream can be further obtained from the resource, regardless of how the resource is implemented.
I would like to implement filesystem access in my project, but it requires some thought.
We could reproduce the classic
open
/read
/write
API, but how should we expose"mount points" for applications?
Ideally, I would like to provide FS access to the local disk, but also have a transparent
access to file storage systems like S3.
The text was updated successfully, but these errors were encountered: