On Oct 22, 2010, at 11:04 AM, John Heenan wrote: > > This slicehost entry uses a REAL FastCGI UNIX socket with the lighttpd > web server: > http://www.web2pyslices.com/main/slices/take_slice/57 > > The entry shows a routes_out example for routes.py but uses web server > URL mapping instead of routes_in.
Thanks, John. I was asking in part because it appears that routes_in might be broken for FastCGI and other interfaces that don't provide PATH_INFO. I have a patch, but no good way to test it (I don't have a FastCGI environment available myself). > > However the potentially beneficial scaling effects of using REAL > FastCGI are lost as web2py converts FastCGI to WGSI internally. That's too bad. Offhand, I'd have guessed that it'd have been easier to write a native FastCGI interface than to write the WSGI adapter. > > There is a slicehost entry that says it is using FastCGI but is really > using WGSI: > http://www.web2pyslices.com/main/slices/take_slice/68 > > John Heenan > > On Oct 22, 12:10 pm, Jonathan Lundell <jlund...@pobox.com> wrote: >> I'd like to hear from anyone who's successfully using web2py with FastCGI, >> especially if you're using routes.py.
