[Zope-Perl] Re: PHP (was zope perl)

[Chris McDonough]

Neat!

I presume you need to work around PHP apps which depend on cookies or other
response features, too.

It would be cool to write a product which not only returned rendered HTML
but was able to munge header data between Zope and PHP so that auth and
cookies and the like would work without needing to do anything special.  The
same approach could be used with Perl CGI scripts.

----- Original Message -----
From: "Joseph Wayne Norton" <norton@alum.mit.edu>
To: "Chris McDonough" <chrism@digicool.com>; <mj@digicool.com>
Sent: Thursday, January 25, 2001 11:36 AM
Subject: Re: [Zope-Perl] zope perl


>
> Yes, I would like to write up a more lengthy HOW-TO. You can check out
> a brief mention of this approach at
> http://www.zope.org/Members/Mamey/PHP . I feel this method could also
> be extended to other languages, etc.
>
> At Thu, 25 Jan 2001 10:08:25 -0500,
> Chris McDonough wrote:
> >
> > I suspect a lot of PHP folks would be bitten by the inability to
"include"
> > other PHP source files from the ZODB, unless you're using DTML to do
that.
> > Are there any other subtle limitations of your approach that you've hit?
> >
>
> We are currently using 2 methods to include other PHP source files.
>
>   - using DTML like one normally does in zope.
>
>   - translating PHP require/include statements into require statements
>   of the form require("http://<apache host>/<zope path>"); where
>   apache is the apache host address and zope path is the path of the
>   php document in the zope namespace.
>
> The current limitations that I am aware of are this approach are:
>
>   - you have to protect the php source from being only visible to your
>   apache webserver ... however, this can be done easily using
>   mod_rewrite.
>
>   - a lot of additional effort may be required by mod_php for a single
>   php document that has a lot of require/include statements
>   ... however, this can be lessened by using mod_rewrite with
>   mod_proxy and setting the appropriate cacheing parameters.
>
>   - if any authentication is required directly within the php
>   "application", it cannot be handled by zope and you have to resort to
>   apache or php for authentication.  I don't know of any good work
>   around at this time.
>
> - joe n.
>
> p.s. As an side, I would prefer not to have to deal with php in the
> first place but using zope/php together provides an easier means to
> migrate an existing application to a pure zope solution.
>
>


----------------------------------------------------------------------------
----


>
> --
> Joseph Norton
>
> norton@alum.mit.edu
> +81-3-3822-6936
> 2-10-7 Tabata, Kita-ku, Tokyo 114-0014, Japan ($B")(B114-0014
$BEl5~ETKL6hEDC<#2CzL\(B10-7)
>
>
>