On Fri, Nov 20, 2009 at 12:21 PM, John Buckman <[email protected]> wrote: > On Nov 19, 2009, at 8:56 AM, Tom Jackson wrote: > >> There is a configuration setting which saves posted files to disk. >> You need the ns_limits maxupload to be large enough, then maxinput >> (not sure which config section) sets an upper limit for in memory >> data. > > Yes, the naviserver people talked about that, but the problem is that then > you get the raw data, that you need to do something with, rather than > temporary files. >
Are you sure? Check out NsConnContent (in driver.c) and Ns_ConnContent (in conn.c), they abstract the location of the data on disk or in memory. This should be transparent to the application. Ns_ConnContent just exports NsConnContent. Also note that streaming to disk is done in the driver prior to selecting a conn thread. The conn thread is where the content handler is located. I cannot imagine how you can short-circuit content handling. > I'm currently trying out naviserver, as they do seem to have solved the > large-file-upload problem that aolserver has. It's working for me, and nsd > process size is staying at 50mb even with multiple gig file uploads being > handled. > Still not sure if you ever tested it on AOLserver 4.5. If this doesn't work, it would be a real surprise the only thing in memory should be the headers and file offsets (see ParseMultiInput). Are you using [ns_conn files]? tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[email protected]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
