Should motion POST API take bytes or a download URL? #10
Replies: 3 comments 4 replies
-
One risk with external download URL: the download could get removed before it's downloaded. |
Beta Was this translation helpful? Give feedback.
-
Certainly valuable but not for MVP. IMO, this feature should belong to a different application that can be built on top of Project motion APIs - and then can add more sources such as FTP support, IPFS support, etc. |
Beta Was this translation helpful? Give feedback.
-
If the rationale is to cope with mid upload disruption then taking in a URL is certainly an option but not the only one. For example, we can push bytes and allow resumption. I also think this is out of the scope for MVP. |
Beta Was this translation helpful? Give feedback.
-
We’ve described the post API as taking bytes, but I wonder if the post API makes better sense as something that gets a URL to fetch data from.
Essentially this would mirror the PULL approach that is eventually used at the SP level.
Long term, this seems way more flexible - especially for very large blobs - but also doesn’t preclude an S3 integration — it would just move storage of the blob above the motion API.
Beta Was this translation helpful? Give feedback.
All reactions