----- Original Message -----
From: Kucera, Rich <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 04, 1999 11:37 AM
Subject: RE: Architecture
> > From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> > right now, ALL JSP pages are compiled in memory. Another feature I and
> >
> I wouldn't want it any other way...all the other servers(ServletExec,
WebLogic,
> Dynamo, JWS) left the generated files laying around and I always had to go
> in there and wipe it all out on more than one occasion--those servers had
lots
> of problems that Orion doesn't have. Leave it in memory, I don't care
to see
> them in the filesystem. Orion has a novel approach.
I disagree. The generated files can be very useful when you're trying to
debug. Deleting them doesn't seem like a big problem, to me. Just create
a batch file to do it.
> > others have requested is to be able to select the java compiler. Right
now
> > it uses the JDK compiler (I think), which is pretty slow. The JIKES
> > compiler is VERY fast at compiling and I think would be great if we
could
> > plug it in.
> >
> I don't know, run Orion on the HotSpot on NT and it's very snappy.
Solaris
> HotSpot is pretty snappy also(even on the reference implementation). Once
> it's cached it's a non-issue, other things are higher priority probably.
Are you saying that HotSpot compiles faster? I agree with the original
poster that Jikes compiler support would be nice. I used another servlet
engine that used Jikes and the page-compiles were almost instant.
Jikes support isn't that big a deal to me, though. While nice, it's pretty
low on my wishlist.
Brien Voorhees
