Return-Path: <esalon@canuck.com>
Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-users@xml.apache.org
Received: (qmail 34034 invoked from network); 7 Apr 2000 12:56:54 -0000
Received: from the-gimp.canuck.com (HELO canuck.com) (204.50.15.12)
  by locus.apache.org with SMTP; 7 Apr 2000 12:56:54 -0000
Received: from esalon ([195.242.59.82])
	by canuck.com (8.9.3/8.9.1) with SMTP id GAA2254254
	for <cocoon-users@xml.apache.org>; Fri, 7 Apr 2000 06:56:48 -0600 (MDT)
Message-ID: <002401bfa090$2d1440a0$0701a8c0@esalon.largemedium.com>
From: "Mark Washeim" <esalon@canuck.com>
To: <cocoon-users@xml.apache.org>
Subject: Re: Enhydra vs Cocoon
Date: Fri, 7 Apr 2000 14:52:44 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

Enhydra is a nice application server. However, it places the onus for
document managment on Application developers. If your working with a
disparate team on larger applications, I don't advise you go that direction.

If your working on nice discrete applications and having the programmer
implement graphic design and html (namely, embed gifs and html/xml/jhtml in
jar files during makes of apps) then it's GREAT.

I like enhydra a lot, but it's not really designed for teams where the
responsibilities for document management are dispersed. For that, you want
Cocoon!

Mark

>Hello,
>
>I surfed the web. I saw Enhydra (http://www.enhydra.org).
>What do you think about it ? What is the difference beteen Enhydra and
>Coccon ?
>I have to choose, what do you advise me ?
>
>Thanks from a beginner.
>
>Herv�
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
>For additional commands, e-mail: cocoon-users-help@xml.apache.org
>