That's weird... I actually had a part in my reply at the end that said
something like "this should work until some code after the filter tries to
access session" :)
Yep, absolutely, if there's a possibility of that then the wrapper is
definitely the way to go.
--
Frank W. Zammetti
Founder and Ch
Frank W. Zammetti wrote:
I can't think of any drawbacks to the filter, and tha's what I would have
suggested. Although, it probably doesn't even have to be as complicated
as a wrapper... simply check for an existing session for the paths you do
want a session created for, and if none is present
I can't think of any drawbacks to the filter, and tha's what I would have
suggested. Although, it probably doesn't even have to be as complicated
as a wrapper... simply check for an existing session for the paths you do
want a session created for, and if none is present go ahead and create it.
I
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 StandardMan
