The keepalive weirdness is gone when we upgraged to a more recent version of wsgiserver. Some time ago. The only known limitation of the current web server is failure of ssl for large uploads (and perhaps downloads?). I run it in production.
Anyway, Tim, here is working on a new web server called Rocket that will soon replace wsgiserver. It is much clearner and fassimoster. massimo On Jan 8, 10:13 am, Timbo <tfarr...@swgen.com> wrote: > I'm curious...how many of you use the built-in webserver (CherryPy's > wsgiserver) as opposed to Apache, LightTPD or Cherokee in web2py and > what do you use it for? If you don't know what I'm talking about, > you're probably using it. > > I've used it in the past for both development on my desktop and > production. I switched to using mod_wsgi+Apache because of some HTTP- > keepalive wierdness (which has been discussed in the past). But if I > didn't have to rely on Apache, that would be one less thing to have to > worry about in our disaster recovery plan.
-- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
