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
First, to make it easier to find download links, we should add one to the navbar.
Second, to improve download speeds and reduce loads on our own server, we want the ability to host the loom files in the cloud, and download from there. However, I am worried about these URLs becoming outdated, for example due to migration. Perhaps we can keep the current code as a "slow alternative mirror"? At the very least for loom files missing this URL field (also with other potential loom-viewer user in mind who do not intend to use a secondary cloud service).
Third, if we keep this fall-backt may be possible to prevent the file-downloading from blocking the server (since it is supposed to be asynchronous and multi-threaded). I should look into that.
download link on navbar
download-from-cloud
make downloading from server a non-blocking sub-process?
The text was updated successfully, but these errors were encountered:
I suggest make this low priority. We can make the downloads instead using links to static files from the Wiki instead, and then apache2 will automatically take care of threading and blocking issues.
First, to make it easier to find download links, we should add one to the navbar.
Second, to improve download speeds and reduce loads on our own server, we want the ability to host the loom files in the cloud, and download from there. However, I am worried about these URLs becoming outdated, for example due to migration. Perhaps we can keep the current code as a "slow alternative mirror"? At the very least for loom files missing this URL field (also with other potential loom-viewer user in mind who do not intend to use a secondary cloud service).
Third, if we keep this fall-backt may be possible to prevent the file-downloading from blocking the server (since it is supposed to be asynchronous and multi-threaded). I should look into that.
The text was updated successfully, but these errors were encountered: