"Kevin A. Burton" wrote:
>
> jon * wrote:
> <snip> I personally wouldn't use ECS as a replacement for JSP. I also
> wouldn't use
> > JSP. ;-) So, what would I use today? I would use a combination of Turbine
> > and WebMacro or Freemarker or I would use Cocoon.
>
> Actually it is more like:
>
> use Cocoon................................... or WebMacro or Freemarker.
I hate to be such a dissenter, but I can imagine that if you had a 1000
row by 10 column XML table that cocoon (particularly cocoon 1.x) was
transforming to HTML it might be fine for one or two concurrent hits.
In our tests we had 50 threads each trying to get such a table 10 times
which completely clobbered our relatively modest server. With ECS this
test "worked" with 6 threads getting the page 10 times and "failed" with
7 threads. On the *same JSERV engine* JSP was able to cope with the 50
threads 10 hits each test relatively easily.
I've never used cocoon, and it seems like a great idea, but at this
point my guess is that performance is going to be a major issue if you
have a busy site with anything other than tiny pages. In the end there's
too many layers on top of a virtual machine that's relatively slow
compared to the raw CPU.
The great thing that ECS has over all these other tools is that it is
extremely simple and elegant. There's no setup or configuration issues
(it's a jar file!), error messages tell you something useful, you're
working in one (real) language, the odds of generating bad HTML because
of a missing tag are small, etc. etc.
Keep up the great work Apache!
--
Cheers,
Derek
_____________________________________________________________________
Derek Scherger Echologic Software Corporation
mailto:[EMAIL PROTECTED] http://www.echologic.com
--
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
