Details
-
Type:
New Feature
-
Status:
Resolved
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 0.5.0
-
Fix Version/s: 0.5.1
-
Component/s: None
-
Labels:None
Description
This is required for the JERM integration.
Be able to provide a URL for a remote asset. When downloading through SEEK, it appears that it is being downloaded just like any other asset, but is infact being proxied via SEEK.
No need to handle authentication at this stage - we can assume that the remote item is available without username/password or other authentication method.
Will require some schema changes to handle different properties on a content-blob.
Application downloads the file then sends to the user. If it can't find it, it sends the cached content in the database.
Not sure how efficient this is, or if there exists a better way of doing it.