|
|
|
|
There are two basic approaches to make PHP on GlassFish Server; one is a PHP on JVM solution like Quercus from Caucho; the other is a bridge to a traditional PHP implementation, like the PHP JavaBridge or LRWPInJava.
|
A quick pass shows a number of references to these approaches:
• Quercus:
Number 9,
John Yeary,
Sebastien,
Gautam,
Davis,
Arun,
Jason.
|
The bridges are technically easier because many PHP packages are not written in PHP and need to be ported, but the PHP-on-JVM solution seems easier to deploy and manage. Of course, another, very practical, solution is to just use a web server like Apache or Sun Web Server :-)
I'm interested in your experience; if you are using PHP on/via GlassFish, please consider posting a comment describing your approach.
somewhere in the glassfish documentation there was a reference to ARP/ART or something like that. I think it had todo with some sort of "apache runtime". Could that functionality be leveraged to pull the php dynamic libraries into the GF space? (can Grizzly play a role here?). Having the GF suite provide a single solution for many languages (including PHP) is obviously an attractive solution.
Posted by mikee on March 08, 2009 at 09:38 AM PDT #
Don't forget to mention the new Project Zero (PHP on JVM):
http://www.projectzero.org/
They are even already running Drupal (including many modules).
Posted by René Leonhardt on March 09, 2009 at 03:32 AM PDT #
re: René - I know about Project Zero but I am only listing solutions that somebody has reported to have used successfully on the GlassFish Server. I just double checked; I see inquiries in the Project Zero mailing list about GlassFish but no replies. Still, it's good to track it. - eduard/o
Posted by Eduardo Pelegri-Llopart on March 09, 2009 at 07:26 AM PDT #