This post originated from an RSS feed registered with Python Buzz by Carlos de la Guardia. Original Post: One reason those "unpythonic" Zope apps still thrive Feed Title: I blog therefore I am Feed URL: http://blog.delaguardia.com.mx/feed.atom Feed Description: A space to put my thoughts into writing. Latest Python Buzz Posts Latest Python Buzz Posts by Carlos de la Guardia Latest Posts From I blog therefore I am

James Duncan Davidson, a well known Rails developer, talks about deployment issues with Rails and how FastCGI is not good enough for that. He thinks having the web application server communicate using HTTP can be a good idea:

"Even better, when you use HTTP as the glue, you suddenly can use a whole host of tools to probe the various parts of your application. You can use curl to probe just your application server. Or even point a browser at it, assuming that you have a clear path through your firewalls and what not. And, if you're really l33t, you can do a manual telnet and make just the request you need --with all the right headers--to simulate exactly a problematic client request."

This is just one of a number of problems that the Zope community already solved years ago. That's why it is fairly easy to deploy an application behind Apache or Squid or Pound or whatever. No zombie processes or mysterious crashes to worry about.

Maturity counts for something. One can scoff at the older guys, but there's always a thing or two to learn from them if you resist the temptation.