Glenn David Sean Taylor wrote:
> Glenn, > > Just wondering about the philosophy behind the StateManager service, and > that it doesn't use the servlet session. > To continue in the spirit of your commit here, are you saying that we > should be moving everything out of the servlet session and into the > StateManager service? We put a lot of state into the servlet session. Do > you recommending that we ditch the standard way of storing state, i.e. > the servlet session, and instead use the StateManager, which manages its > own state into a singleton non-sync'd hashmap? > > Just wondering if this is the best approach. Some cons: > > - have to duplicate a service that already exists > - no standard life cycle events from servlet api > - can't take advantage of servlet session sharing from some server impls > - its not standard > > I believe the pro is: > > - the servlet specification doesn't support 2 browser sessions on the > same machine with cookies turned on Why are we trying to solve a problem that we do not control? Tomcat does the session management, and we do not want to use it? I am getting really close to a -1. So please tell me why we are solving this problem! > <snip> > David > > Paul Spencer -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
