Hi, I've used both the reverse proxy and the fastcgi mechanisms (on www.ekno.com and www.ekit.com, respectively) and there's no comparision - fastcgi is _far_ superior. It's much faster, it's less load on the apache machine, and you don't end up with the apache server eating things like the remote machine name. I wouldn't recommend the reverse proxy approach to anyone. Anthony

...

...

Tom Deprez wrote Hi all,

No, this is not a question on how to do it. All the how-to's available clearly explain this... it just an informational question and I hope somebody can give me a straight answer.

In reading Jeff Shelton's Python conference summaries (by the way, thanks Jeff for doing this! Now, people who're not able (because of their job, ...) to go to this conference can still pick something up! Great!) I read the following :

In Jim's opinion, the "preferred way" to hook into Apache will soon become FastCGI rather than PCGI.

Well, I can understand that FastCGI is better than PCGI, but I read (and implemented) a how-to of anser (Using Apache with ZServer (Not Zope cgi)) in which he explains the use of ProxyPass and ProxyPassReverse. Well, this mehtod looks to me really handy. You use all the positive things, because you can use Apache, but also the fast ZServer.

So, now, you'll understand that I'm a little bit confused. What is now the best way ... using FastCGI or ProxyPass....? What are the differences between the two? What are the pro's and con's?

Regards, Tom.

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )

-- Anthony Baxter <anthony@interlink.com.au> It's never too late to have a happy childhood.