That's exactly it... I'm asking the question "why would one go with
enhydra and not tomcat?"
xmlc is one answer, but not really since xmlc has long since been
extracted away from enhydra and can now be used with tomcat, jboss or
what have you...
at one time, enhydra had a rich superset of features that were absent in
tomcat. I'm just wondering if folks feel that there's still good value
in enhydra when compared with tomcat.
David
Terry Steichen wrote:
David,
But of course Enhydra uses a servlet container (such as Tomcat), so how do
you compare the two?
Regards,
Terry
----- Original Message -----
From: "David H. Young" <david@xxxxxxxxx>
To: <enhydra@xxxxxxxxxxx>
Sent: Tuesday, April 22, 2003 11:05 AM
Subject: Enhydra: tomcat vs. enhydra
Hi,
I'm giving a presentation on xmlc at the New Mexico JUG next week. I've
been asked to talk about Enhydra, and since it's been awhile, I thought
I'd ping everybody about how Enhydra compares to Tomcat these days. I'm
sure I'll get questions about that topic and since it's been awhile
since I've worked with Enhydra, I'd love any perspectives that anybody
would like to throw out there...
I've always thought of it as 1) a complete architecture for 3-tier
servlet development, including jdbc connection manager and 2) a superior
admin tool.
Thanks,
David
_______________________________________________
Enhydra mailing list
Enhydra@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/enhydra
_______________________________________________
Enhydra mailing list
Enhydra@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/enhydra
| 