my web application has three separate interfaces: an html ui, webdav,
and a custom http/xml protocol. clients of the latter two interfaces are
unaware of the http session, so i'd prefer that sessions not even be
constructed when requests come in through those interfaces.
i see that StandardManager and PersistentManager have maxActiveSessions
attributes, which i could potentially set to 0, but that isn't a
solution since i *do* want to have sessions for the html ui.
short of writing a new implementation of Manager, is there a way for me
to specify that sessions should not be created for, say, all requests to
/foo/*?
one idea was a filter that wraps the request with a class that overrides
getSession. are there any drawbacks to that approach?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
