-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David,
David Delbecq wrote: > For now, the layout is Filter that check userPrincipal. If user > principal is not null for the first time, issues that check, mark > that user got checked for next times, in session, and continue query. > However, if i could mark the session as "need upgrade" upon login, > this would make things, i think, easier to manage as filter would > only need to look for that "need upgrade" flag. I think you'll find that you're just breaking your filter into two separate filters: you'd have one that check to see if the session "needs an upgrade", and then another one to "upgrade" it. Since the functionality is all related, I'm not sure if there's a good reason not to keep it all together. Do you have any particular complaints about your existing strategy? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGybYb9CaO5/Lv0PARAvhKAJ98z4exrOeiSHS+0eQ2IlYWYl17lACeK5mF JKrxaBpWuU+0DsXoST1jKbU= =ByA4 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
