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
We'd like to have a routing to "obtain" a new file, given GUID and file type, within the main webapp. At the moment, we haven't figure out how to actually obtain new files from AAPB API, so for now the function can just create some dummy files under some random subdirectory.
But the newly obtained file should be indexed into the DB, and can be retrieved via mapper route.
The text was updated successfully, but these errors were encountered:
"obtain" function can take a fair amount of time when actually downloading a few hundreds MB (or a few GB) file. Hence we might need to consider a internal function that performs asynchronous download in the future.
we can change the mapper function to call the "obtain" function when the requested GUID is not found in the DB. Combining this idea with the above, handling async download can be tricky if mapper route needs to immediately response.
At the moment, we have <5,000 video files in our data server, but in the future, when we "obtain" too many files, we might need to delete some files to fit in the disk space. We need to decide a caching strategy for that (LRU? LFU? FIFO?) but for any kind of caching, we probably need a few additional columns in the DB scheme to record "obtain" time and "last-used" time.
We'd like to have a routing to "obtain" a new file, given GUID and file type, within the main webapp. At the moment, we haven't figure out how to actually obtain new files from AAPB API, so for now the function can just create some dummy files under some random subdirectory.
But the newly obtained file should be indexed into the DB, and can be retrieved via
mapper
route.The text was updated successfully, but these errors were encountered: