Breaking it down: The magic of multipart file uploads
Posted by Local_Ad_6109@reddit | programming | View on Reddit | 11 comments
Posted by Local_Ad_6109@reddit | programming | View on Reddit | 11 comments
AyrA_ch@reddit
The article doesn't describes multipart at all. It describes a chunked upload.
A multipart file upload is a traditional upload that uses the multipart/form-data encoding.
palmin@reddit
Words can mean more than one thing and it seems reasonable to describe something that uploads things in multiple parts at multipart upload.
Note how AWS S3 multipart upload has nothing to do with multipart/form-data.
Jmc_da_boss@reddit
This just means Amazon is dumb as hell. A fact that has been well known for years
eldreth@reddit
I'm not sure citing AWS' naming conventions/marketing language is a W.
Jugales@reddit
It’s like Databricks with their ~~scheduled batches~~ “streaming”
palmin@reddit
Life is going to be hard if you get confused when people use the same words for different things. This is a core part of natural language.
eldreth@reddit
Uh huh. Just wait until you find out what they mean by server-less. ;)
andy_a904guy_com@reddit
AWS is the king of calling shit by the wrong name. LOL
AyrA_ch@reddit
Which is exactly why calling a chunked upload a "multipart" is stupid and confusing
guest271314@reddit
Nowadays we have upload streaming using WHATWG Fetch with duplex set to half Streaming requests with the fetch API.
guest271314@reddit
Re
It's basically possible to create indefinite upload stream using
fetch()withduplex:"half"set and the body is aReadableStream; e.g., Test infinite Opus stream.