>>> Yup, and I use them. This is a bit different, in two ways:
>>> - pure servlet container, since there's nothing tomcat-specific
>>How are you handling session affinity and/or migration?
> A simple way: the same rule will always redirect to the same server.
OK. So that's one limitation compared to doing clustering at the Valve
level.
>>That [rules-based] aspect would seem to be something to discuss
>> with Filip. I think that it would be useful to add that
>> concept to the Tomcat work.
>Maybe: discussion can't hurt, which I why I brought this up ;) I've
>taken care to make my stuff portable to other servlet containers, not
>just tomcat, so I don't want to tie it tightly into tomcat.
Maybe your rules system could be factored out into a place where it could
work with Filip's code. Don't know. Just encouraging you to talk with
Filip. :-)
> BTW, to your list of other web components for perhaps a WebApp Commons,
> I would maybe add some things from the log4j-sandbox that I've been
> working on. There are servlets there that I hope will some day grow
> into a log4j administration webapp.
I'm thinking that it might be a good idea to have a WebApp Commons, either
in Commons or as a separate space. There has got to be a lot of code that
people would contribute to such as space.
My first contribution would be the generic Listener class that I wrote,
which provides a nice framework for adding Listener-based functionality, and
on its own provides insight into when events happen.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
