Leon Waldman wrote: > I'm not sure if web.py is suitable to CGI usage because it tends to execute > the dev web-server when executed and output the requests made to stdout that > would be where it should output the html it self to be delivered to the > Apache CGI handler.
It's perfectly suitable for CGI! Here's the docstring for web.application.run: """ Starts handling requests. If called in a CGI or FastCGI context, it will follow that protocol. If called from the command line, it will start an HTTP server on the port named in the first command line argument, or, if there is no argument, on port 8080. `middleware` is a list of WSGI middleware which is applied to the resulting WSGI function. """ > You could build your app in pure python outputting the html code directly as > a simple print. Why do that, when templates are so much nicer? Regards, -- Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
