Re: Enhydra: tomcat vs. enhydra

David Li<david@xxxxxxxxxxxxxxxxx> wrote:

>Session Manager. Enhydra still has better session manager then Tomcat. 
>However, I think Tomcat supports a plug-in architecture for session and
>it's possible to port Enhydra's session manager to Tomcat.

Why do you think SessionManager is better the session management under
Tomcat ? (are you talking about KeywordValue implementation ?)

>It's probably easy to take the view point of Enhydra SuperServlet as a 
>Framework the Enhydra as app server. In this view, Enhydra and Tomcat 
>should be complement instead of competing. Asking Enhydra vs Tomcat is 
>kind of like asking Struts vs Tomcat.

Completely agree.

>The other tools for Enhydra, namely XMLC, DODS and others are OK to be 
>used on top of Tomcat.

Just what i'm doing right now...

>I think the Enhydra 6.0 is heading the direction of making Enhydra a 
>framework.

I would like to see it!
Right now i'm switching my SuperServlet web apps to 'standard' webapp
that use XMLC at the presentation, but i can tell you is almost a pain
in the ass. Previously i was used to run superservlet within standard
Servlet container (outside Enhydra app server) and that was not
strightforward... i can tell you. (Just as a not i've had to do that for
maintenance reason and after all for performance reasons)

I really like Enydra... but Enhyra as a framework not as AppServer.

How are the plan for the Enhydra future ?

Regards,
Thelmo