From: Reini U. <ru...@x-...> - 2001-07-10 20:03:43
|
Alby Lash schrieb: > As far as I understand, jsp/servlet architecture is a lot faster than > perl/php/asp etc. Once the server engine interprets/compiles the script the > code becomes cached and operates like a real compiled application, and less > like a bunch of self referential scripts. mod_perl Apache::Registry does this also; and is closer to the apache API. (sockets vs direct in-proc calls) nevertheless good JSP engines (resin http://www.caucho.com/products/resin/) are still faster, because the optimizing java compiler can do better than the php or perl compiler. but i'll never do any java, I'll rather kill my time with php than with java. And I still don't trust the java memory management, similar to mswindows memory management, which makes it "hard" to run on production servers, esp with 1000's of vhosts. (even though it still does only sockets). BTW: mod_lisp is similar to jsp/servlets. resin just has a better code and template caching scheme than mod_lisp, which has none yet. > ----- Original Message ----- > From: "Peter Bowyer" <re...@f2...> > To: <bin...@li...> > Sent: Tuesday, July 10, 2001 2:47 PM > Subject: Re: [binarycloud-dev] capwiz > > > At 03:49 PM 7/10/01 +0100, you wrote: > > >I really wanted to use common lisp or mod_perl (mason,embperl or axkit) > > >for my big e-commerce site i'm working on, but they cannot afford > > >server hosting for the beginning, so I cannot use mod_perl (nor > > >lisp/zope/jsp), > > >only php. > > > > And what's wrong with PHP? > > > > Admittedly I've never done any large scale development, so what is the > > reason for wishing to use something else? |