Hey Alex, 2010/2/24 Alex Sadovsky <[email protected]>: > Hi Wim! > > Thanks for the config option. And no, my next question will be: "If > you use so much memory to upload a large file, why do you return a > temporary file in the file system and not a memory buffer?" and after > that "What about a callback function when next chunk arrives?"
How predictable though :-) The uncomplicated answer to the first question is: we never cared about optimizing file uploads, until now. Wim already curated the memory usage so that now memory usage is not dependent on file size (in our development branch). The second question, which is a repeat of a popular feature request, is a bit more difficult, since it cross-cuts from the connector internals to Wt. For example, the http connector currently waits until the entire post is received before notifying the Wt controller, and this is commonly done to protect against slow connections locking up threads (as the http connector is entirely asynchronous, while Wt itself is synchronous). No doubt it can be solved, but we must make sure we do not entangle the connector and Wt too much. Regards, koen ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
