Re: Re: Enhydra: tomcat vs. enhydra

> > 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 ?)

The implementation includes write to disk and write to DB for 
fail-over. Tomcat's session manager is basic. I am not talking about 
interface difference but implementation difference.

> > 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.

Are you using XMLC 2.2? It's pretty straight forward to use XMLC 2.2 
with Tomcat. In fact, Tomcat is used as the development environment of 
XMLC 2.2. ;) There is an example in 2.2 distribution.

More XMLC 2.2 promotion here:

http://debian-sf.objectweb.org/projects/xmlc

> 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 thought the 5.0 has made that easy. There was a patch needed for 3.x 
which I have posted here. I think that's integrated into 5.x already.

> I really like Enydra... but Enhyra as a framework not as AppServer.
>
> How are the plan for the Enhydra future ?

According to Madl Alfred, that's the direction of Enhydra 6.0.

David