On Sat, May 07, 2011 at 01:07:40AM -0400, Nick Mathewson wrote: > *lots of text here*
One of the ways nginx deals with very large streams of data is to actually spool the data to file. By default this is turned off. But this may be a simple solution to all of these problems. The spooling is transparent to the user, but with libevent we can expose a little bit more information (since we're dealing with applications utilizing, instead of scripts or whatever being called static) about where the file is or something to the likes.. The configuration directive is explained here: http://wiki.nginx.org/HttpCoreModule#client_body_temp_path In the case of systems with mmap, it would be trivial for the callback to see the file as just memory. Being a toggle, the user would have to understand the tradeoffs of spooling, maybe having some use of os-dependent implementations of disk aio. We would have to somehow figure how to deal with cleanup. *********************************************************************** To unsubscribe, send an e-mail to majord...@freehaven.net with unsubscribe libevent-users in the body.
