cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Maring <>
Subject RE: Enhydra vs Cocoon - with new Cocoon idea
Date Mon, 10 Apr 2000 11:24:23 GMT
I'm testimate to that brother.  I looked into Enhydra a while back and saw a
crapload (purely scientific term) of promises of having it become the
ultimate application server of web technology.  But I became the typical
dear caught in the headlights of a strong marketing department.  Despite the
OpenSource approach, it smelled oddly commercial.  I got scared and ran.  I
really don't know where they stand now, so I'm certianly not an expert.  I
opted for a sense of prurity, so I use Jonas by itself as an EJB application
server, and Jonathan by itself as an ORB (ocassionaly VisiBroker for
customer demands).  For a complete distributed web application solution, I
find that Cocoon, Tomcat, Jonas, and Jonathan all work rather nicely as they
are.  Not that there is not room for improvement. :-)

I'm not sure if it would be wise for Cocoon to try to become an EJB
container as well though.

Here's an idea for Cocoon though.  How about a way to stick a document
manager at the front of the process that can check the state of change on
original data, and point a reference to a pre-Cocooned xhtml page if no
state has changed.  I'm just thinking of ways to limit the requirement for
processing, if even just formatting, on every request.  i.e. Have a sort of
automated change management procedure that can automatically start the
generation of new *.html files from various events.  Those events could
either be timed, or based on file changes, like Suzie from PR just changed
an aricle in the XML.

The thought is that for some pages, they may only change once in a hundred
requests, and it seems silly to process every request in a servlet container
if the page never changed.

--Steve Maring

-----Original Message-----
From: Stefano Mazzocchi
Sent: 4/9/00 7:26 AM
Subject: Re: Enhydra vs Cocoon

"David H. Young" wrote:


> As always, it comes down to picking your poison.  And figuring out the
> nature of your project, the capabilities of your team and how you
> different groups to different parts of the project.

Totally true.

Anyway, to be extremely honest with you, I don't have _any_ problem to
have open source projects that are based on the same technology (Enhydra
is based on Apache JServ) and are competing in other grounds (XML).

What I found _offensive_ and utterly provocative is that "leading"
marketing shit in all your advertising. I also find "scary" the need for
an open source project to be -advertised- on slashdot to gain momentum.

I'll tell you a story: NewAtlanta people used to have a signature on
their emails such as "the leading providers for servlet technology".
When people started to laught at that, they removed it.

Once the community is laughing at you, it's pretty hard to back it up,
don't you think? ;-)

Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<>                             Friedrich Nietzsche
 Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message