well I could also try that from my
well, I could also try that from my backend (without workers) but my experience (maybe I am just stupid) was that the file is buffered entirely due to the client uploading faster than the r2/s3 connection being build up + posted
7 Replies
@kian do you get what I mean? Maybe you have some ideas here, because streaming would be ideal.
How streaming is implemented on a application/network level is beyond me - a question for someone much smarter than myself haha
I don't think it's particularly avoidable in your case. If users aren't uploading the file but rather giving it to you to upload, you'll always need to have the file yourself I suppose
yes, that's what I fear will also happen to the workers. I think I'll just try with the memory held option and a small file size limit
What issue do you think will happen with Workers?
It'd be the same as presigned except instead of the presigned URL, you give them the Worker URL
The worker would have to buffer the whole uploaded file probably before being able to upload it
I don't see why
Cloudflare's earlier 'layers' of webserver might do but the Worker will have no issues since it's not being buffered into the Worker's memory
https://developers.cloudflare.com/workers/learning/using-streams/
Yes I am currently trying that but on my normal backend. Seems like with http2 there are some possibilities of real streaming