Hi Marcel, when uploaded file is spooled to the filesystem, user callback should still be called, and POST content be exposed to the caller. I see two options: 1. memory-map spooled file. conn->content, conn->content_len will point to the memory mapped file in the same way as it was a usual small POST request 2. add conn->filep attribute which will be a "FILE *" stream pointer of uploaded file. Either conn->content or conn->filep might hold uploaded data.
Could you describe your use case please, what uploads are used for, how frequently, how large? On Thu, May 8, 2014 at 2:42 PM, Marcel Wirtz <[email protected]> wrote: > Hello, > > we try to implement file uploading for our application using LibMongoose, > but we have some problems with files larger than 530 MB. > > 1) Server returns "400 Bad request". > 2) The used RAM grows with the upload up to more than 530 MB. > 3) If you start a second upload it could be more than 1060 MB in RAM > > It would be practical not to store the whole fileupload in RAM and to > allow to write the file part by part and not only at once when complete. > > > > -- > You received this message because you are subscribed to the Google Groups > "mongoose-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/mongoose-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "mongoose-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mongoose-users. For more options, visit https://groups.google.com/d/optout.
