the reason I wanted to expose these methods at the Manager level is that it makes using various session manager implementations more seamless, without having to cast to specific impl classes.
Yes I agree. I was just poiting out the discrepancies that this change introduced with Craig's original design. Actually, the only real optimization that can be done in the next Tomcat, assuming the current architecture remains, is to remove all the redundant abstract types (interfaces and abstract classes) to optimize away any useless RTTI and casts (now that the architecture has been real world tested for a while, we know what is useful and what is not).
Also, this will "force" future manager impls to use consistent method signatures and names (ie., use getExpiredSessions() vs. getExpired() or something like that).
You're right that the basic manager does not care about expired sessions, but that's why it is abstract.
If a particular manager impl does not care about expired sessions, they can simply return zero. ;-)
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
