Henri Gomez wrote:
Andrew C. Oliver wrote:

I thought this might be interesting to some folks... They're porting PHP to Java...

-Andy

-------- Original Message --------
Subject: RE: [JBoss-dev] PHP
Date: Thu, 9 Jan 2003 19:13:23 -0500
From: "marc fleury" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>

Yeah that was my first impulse, to have a PHP interpreter in JBoss so
that we could leverage all the PHP thingies out there.

clearly the problem with PHP is that the guys who do the front end
modules and app DON"T KNOW THE FIRST THING ABOUT COMPONENTS and the
benefits it brings in caching (see whole argument on EJB in BLUE).
Putting EJB behind the whole mess would be great. PHP can talk java but
it is out of process so that you go back to serialization and LOSE the
benefit of caching. Period. So clearly having the PHP code interpreted
in java would be great as you access the db data in cache.

The problem is that the libraries used need to be ported too and that
becomes a pain. I am really serious with the porting as Julien will be
payed for this.

That's excellent for site which have allready tons of PHP code and
need to switch slowly from PHP to JSP/Servlets.

Also for sites having PHP on some boxes but didn't have PHP binaries on
the target machine (ie iSeries)



Very late, but...

I think the right approach would be to change the PHP templates to ensure that they produce "proper" XML (be it XHTML or whatever language suits you) and the use it in a Cocoon Reader, or XSLT-it, or whatever, from as far away from the original box as you can stay. If the original apps are cleanly written (i.e. with themes, etc.) it should be simple

Instead of importing PHP nightmares into java, you would have to deal with (more or less) clean data interfaces.

Don't ever allow anybody to lead you to think that "fixing" legacy apps is your problem ;-)

This meta-knowledge has worked a lot for me. It you absolutely must, just multiply your wages times 10 and pray ;-)

Regards,
Santiago


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to