-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Store large items as files #5
Comments
File types are like literal types, they need to be pre-defined.
These are somewhat similar to references. We might have |
|
Can we do Probably not, due to confluence. When the solver has the constraint |
Note that the type of a file does not imply an encoding. Text can be stored as utf8 or uft16 or whatever. Images can be stored as PNG or JPEG, etc. |
(files can't do insert/delete like
|
File API:
Format API:
or
or
|
Not seeing a pressing need for this, for the moment. |
This is definitely wrong. The whole point of files is that they may be too big to be |
raw interface:
|
Would like to record the type of the file. For each type
|
Big files are not quickly hashable. So it seems like the best approach is to make files mutable and assign UUIDs to them randomly.
Create a type
File
, withFile <= Entity
.Possibly: create a
filetype
keyword, likeopentype
, that would generate subtypes ofFile
.Possibly: predefined file types for a library of file operations, e.g. image sizes, media durations, etc.
The text was updated successfully, but these errors were encountered: