mikefilonov wrote > Thank you for the link. It is a useful example of how ajax upload can be > implemented in Seaside. > > However, by looking at the code which works without nginx plugin I see the > project does not change the mechanism of request reading, meaning if you > upload 1Gb file you still need 1Gb of RAM to store WAFile rawContent.
Oh. I thought NAFileUploadNginx was code to use nginx to store uploaded data directly to disk which would prevent the image from seeing the uploaded data and thereby not change the RAM requirements really at all. Which was what you were considering using in your second message in the thread. -- View this message in context: http://forum.world.st/RAM-efficient-alternative-to-ZnMultiPartFormDataEntity-tp4834528p4834908.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
