Hi everybody. I hope this is the appropriate forum for this question.
Currently I am doing distributed session management with a hacked up
jserv that can persist serialized sessions in the DB if they are deemed
"dirty".
The session id encodes information regarding, among other things, which
machine
in the cluster the session is currently bound to. Thus it is easy to detect
a failed-over
session and suck it back in from the DB.
I am attempting to get out of jserv land and port the application over to
tomcat.
I looked at the source and it seems like that if i wanted to implement the
current
solution on tomcat that i would have to end up hacking tomcat which is not
what i want
to do. It seems that StandardSessionInterceptor, StandardManager,
SessionIdGenerator and
Session would have to be reimplemented to support what I would like to do. I
don't have
a problem doing this but I don't want to end up with a divergent tomcat code
base (which
is exactly what happend with jserv). I am new to tomcat so hopefully I am
missing something.
Could anyone provide some suggestions on the a course of action which would
keep me
on the normal tomcat dev path? It would be much appreciated.
thanks a lot.
topher
