[ale] PHP vs. J2EE
Christopher Fowler
cfowler at outpostsentinel.com
Thu Mar 20 13:01:17 EST 2003
Its all production and has to run on UNIX. Not necessarily Linux.
Compiling Apache + PHP and getting it working for FreeBSD 5.0 was a
challenge enough.
But I guess Tomcat would pose a similar task.
On Thu, 2003-03-20 at 12:53, John Wells wrote:
> Indeed, but it's listed as "experimental" on the PHP project, and I found
> it completely broken in 4.2.3 and 4.3.0 (have logged ticket at
> http://bugs.php.net). I could instantiate system classes, but custom
> classes would cause Apache to go down hard with a segfault.
>
> If you're designing this for production, I'd stay away from PHP/Java
> integration. If not, it's definitely fun to play with.
>
> If you have to have java, go with a tomcat container.
>
> John
>
> C I said:
> > I haven't played with it in a while but PHP has the
> > ability to access Java classes directly. So you could
> > have all you logic in Java on the backend and just
> > have the PHP request the needed info and the Java will
> > return the data. Was a lot of fun to play with.
> >
> > CI
>
>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale
More information about the Ale
mailing list