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" <[EMAIL PROTECTED]> > Antworten an: [EMAIL PROTECTED] > Datum: Thu, 9 Jan 2003 15:34:10 -0500 > An: <[EMAIL PROTECTED]> > Betreff: RE: [JBoss-dev] PHP > > IWE. Go Go Julien Viet! > >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED]]On Behalf Of Matt >> Munz >> Sent: Thursday, January 09, 2003 3:16 PM >> To: [EMAIL PROTECTED] >> 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:[EMAIL PROTECTED]] >> Sent: Thursday, January 09, 2003 2:39 PM >> To: [EMAIL PROTECTED] >> 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 >> [EMAIL PROTECTED] >> 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 > [EMAIL PROTECTED] > 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 > [EMAIL PROTECTED] > 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 [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
