On Mon, 15 Oct 2007 16:10:06 +0200 "Daniel Brahneborg" <[EMAIL PROTECTED]> wrote:
> Thanks for the replies. > > The fact that Mongrel shouldn't be the first one to get the POST/PUT data > was a good point that I hadn't thought of. However, even when talking > directly to Mongrel, the memory consumption of the application increases > until it crashes if too much data is sent. In my case, I was sending a 500MB > file from a Webdav client. At some point all of it was loaded into RAM, which > doesn't work. > > Are there any more productive alternatives than writing the entire thing > from scratch in C? Please? :) Daniel, Mongrel is a library. Not a server. I just wrote a server with the library. Look past mongrel_rails and into the heart of the RDoc. You will find your answer there. (Probably somewhere in the place where it mentions handlers and filters.) -- Zed A. Shaw - Hate: http://savingtheinternetwithhate.com/ - Good: http://www.zedshaw.com/ - Evil: http://yearofevil.com/ _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
