You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@jakarta.apache.org by "Andrew C. Oliver" <ac...@apache.org> on 2003/01/10 14:06:08 UTC
(PHP interperated via Java) [Fwd: RE: [JBoss-dev] PHP]
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" <ma...@jboss.org>
Reply-To: jboss-development@lists.sourceforge.net
To: <jb...@lists.sourceforge.net>
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.
marcf
> -----Original Message-----
> From: jboss-development-admin@lists.sourceforge.net
> [mailto:jboss-development-admin@lists.sourceforge.net] On
> Behalf Of Holger Baxmann
> Sent: Thursday, January 09, 2003 6:20 PM
> To: jboss-development@lists.sourceforge.net
> Subject: Re: [JBoss-dev] PHP
>
>
> anybody thought about integrating php (and this way the
> cms-whatever-this-is
> thingy) into the the containers? maybe by calling the zend
> engine natively?
>
> layer rules ...
>
> just an idea ..
>
> bax
>
> > Von: "Bill Burke" <bi...@jboss.org>
> > Antworten an: jboss-development@lists.sourceforge.net
> > Datum: Thu, 9 Jan 2003 15:34:10 -0500
> > An: <jb...@lists.sourceforge.net>
> > Betreff: RE: [JBoss-dev] PHP
> >
> > IWE. Go Go Julien Viet!
> >
> >> -----Original Message-----
> >> From: jboss-development-admin@lists.sourceforge.net
> >> [mailto:jboss-development-admin@lists.sourceforge.net]On Behalf Of
> >> Matt Munz
> >> Sent: Thursday, January 09, 2003 3:16 PM
> >> To: jboss-development@lists.sourceforge.net
> >> Subject: RE: [JBoss-dev] PHP
> >>
> >>
> >> Marc & group,
> >>
> >> Thanks for the details.
> >>
> >>> We tried to rewrite
> >>> the forums (which we did) and it took us for ever due to the
> >>> publishing framework getting in the way.
> >>
> >> My good friend Google just explained "CMS publishing" to
> me, and I
> >> think I understand the issue. It is not PHP vs. J2EE, but
> Post-Nuke
> >> vs. a J2EE-based CMS that apparently DNE.
> >>
> >> Not the best situation...
> >>
> >> - Matt
> >>
> >> -----Original Message-----
> >> From: marc fleury [mailto:marc.fleury@jboss.org]
> >> Sent: Thursday, January 09, 2003 2:39 PM
> >> To: jboss-development@lists.sourceforge.net
> >> Subject: RE: [JBoss-dev] PHP
> >>
> >>
> >>> Bill,
> >>>
> >>> Don't worry, I'm not going to blast you for not "eating
> your own dog
> >>> food".
> >>
> >> you should.
> >>
> >>>> JSP/Servlets/J2EE is better, but PostNuke is a good Content
> >>> Management
> >>>> System.
> >>>
> >>> This statement, in and of itself, is a rationale for using J2EE
> >>> instead of PHP ;) Could you divulge the precise
> >>> reason(s) for choosing Post-Nuke? (I can think of many
> factors that
> >>> often outweigh technical superiority -- time, money,
> expedience, IP
> >>> issues... was it one of these?)
> >>
> >> the real reason is that the APPLICATION IS THERE. We tried to
> >> rewrite the forums (which we did) and it took us for ever
> due to the
> >> publishing framework getting in the way. The problem we
> have is that
> >> PostNuke is a bunch of PHP files with direct DB access in
> it and we
> >> are having scalability nightmares. Our machine used to be 15%
> >> utilization max (slashdot was 50%) due TO THE CACHES IN
> JBOSS. And
> >> without it, we have 100 people on the website and the machine is
> >> pegged.
> >>
> >> So the application is there so we use it. We need it NOW. Julien
> >> viet, who was writing the forums, is now on JBoss payroll
> and will be
> >> working on JNUKE. A straight port of PHP functionality to
> JBoss. PHP
> >> is ugly and functional, my kind of code but at the end of
> the day it
> >> doesn't scale well at all due to all the crap they do.
> EJB are good
> >> things :)
> >>
> >> Peace,
> >>
> >> marcf
> >>
> >>
> >>
> >>
> >> -------------------------------------------------------
> >> This SF.NET email is sponsored by:
> >> SourceForge Enterprise Edition + IBM + LinuxWorld =
> Something 2 See!
> >> http://www.vasoftware.com
> >> _______________________________________________
> >> Jboss-development mailing list
> >> Jboss-development@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/jboss-development
> >>
> >>
> >> -------------------------------------------------------
> >> This SF.NET email is sponsored by:
> >> SourceForge Enterprise Edition + IBM + LinuxWorld
> > http://www.vasoftware.com
> > _______________________________________________
> > Jboss-development mailing list
> Jboss-development@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
> >
> >
> > -------------------------------------------------------
> > This SF.NET email is sponsored by:
> > SourceForge Enterprise Edition + IBM + LinuxWorld =
> Something 2 See!
> > http://www.vasoftware.com
> > _______________________________________________
> > Jboss-development mailing list
> Jboss-development@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
> >
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something
> 2 See! http://www.vasoftware.com
> _______________________________________________
> Jboss-development mailing list Jboss-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Jboss-development mailing list
Jboss-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: (PHP interperated via Java) [Fwd: RE: [JBoss-dev] PHP]
Posted by Santiago Gala <sg...@hisitech.com>.
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" <ma...@jboss.org>
>> Reply-To: jboss-development@lists.sourceforge.net
>> To: <jb...@lists.sourceforge.net>
>>
>> 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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: (PHP interperated via Java) [Fwd: RE: [JBoss-dev] PHP]
Posted by Henri Gomez <hg...@apache.org>.
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" <ma...@jboss.org>
> Reply-To: jboss-development@lists.sourceforge.net
> To: <jb...@lists.sourceforge.net>
>
> 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)
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: (PHP interperated via Java) [Fwd: RE: [JBoss-dev] PHP]
Posted by Jon Scott Stevens <jo...@latchkey.com>.
on 2003/1/10 9:54 AM, "Andrew C. Oliver" <ac...@apache.org> wrote:
> But interesting no? ;-)
Not anymore interesting than Jython...
"Hey, let's re-write every language in Java just to be interesting!"
I'm waiting for the C implementation in Java. Not.
-jon
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: (PHP interperated via Java) [Fwd: RE: [JBoss-dev] PHP]
Posted by "Andrew C. Oliver" <ac...@apache.org>.
But interesting no? ;-)
Jon Scott Stevens wrote:
>on 2003/1/10 5:06 AM, "Andrew C. Oliver" <ac...@apache.org> wrote:
>
>
>
>>I thought this might be interesting to some folks... They're porting
>>PHP to Java...
>>
>>-Andy
>>
>>
>
>Yea, it is called JSP w/ scriptlets.
>
>This is a stupid idea.
>
>-jon
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: (PHP interperated via Java) [Fwd: RE: [JBoss-dev] PHP]
Posted by Henri Yandell <ba...@generationjava.com>.
On Fri, 10 Jan 2003, Jon Scott Stevens wrote:
> on 2003/1/10 5:06 AM, "Andrew C. Oliver" <ac...@apache.org> wrote:
>
> > I thought this might be interesting to some folks... They're porting
> > PHP to Java...
>
> Yea, it is called JSP w/ scriptlets.
JSP2.0 w/ JSTL. Full of ${blah} variables to make the PHP fan happy.
> This is a stupid idea.
Agreed. I don't know of anything that PHP has to offer to a JVM. PHP-OO is
a copy of Java's style generally, much of the ease of PHP is doable with
latest JSPs now, PHPs painful admin model is thankfully easier in Java,
and PHPs multitude of db-dependent [PEAR not being dominant] functions are
thankfully not in existence in Java.
The only thing PHP has over Java is the ease with which it fits in an
Apache server. It'd be much nicer to keep improving on [Sam's I think] the
PHP->Java link and defining a subset of PHP so that apache users can use
Java without having to link to another application.
Hen
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: (PHP interperated via Java) [Fwd: RE: [JBoss-dev] PHP]
Posted by Jon Scott Stevens <jo...@latchkey.com>.
on 2003/1/10 5:06 AM, "Andrew C. Oliver" <ac...@apache.org> wrote:
> I thought this might be interesting to some folks... They're porting
> PHP to Java...
>
> -Andy
Yea, it is called JSP w/ scriptlets.
This is a stupid idea.
-jon
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>