> markw@mohawksoft.com wrote: >> This isn't a question about "how to use" the system in my servlet, it is >> a >> question about the best approach to implement different functionality in >> the server. > > Ok, I understand. I suggest forgetting about these design ideas, this is > bad design IMO.
I would *REALLY* like to understand why you say it is a bad design. It is my humble opinion that HttpSession is broken. So, I think we have to very different perspectives, and I'd like to understand yours. >From my point of view, I think relying on the load balancer to keep session sticky, or forcing the entire web cluster to replicate is crazy. I have a system, it is not a database, but sort of acts like one. It is designed as a shared object cache system. I would like to use it to manage HttpSessions. It uses a lock/retrieve and unlock/update interface. When the session starts, it is locked. When the session is done, it is unlocked and updated. It should incur no more network bandwidth than the cluster implementation, but does not force all machines to have all sessions either. I can use a serial number system to keep from invalidating the existing HttpSession object if it is already up to date. This will reduce network traffic if valid sessions exist on the target machines. > If you stil want to do it, maybe you can try doing your > stuff directly in your DB using the session id that Tomcat gives you, > and otherwise not using the session object. I already have that, but to be more widely useful, obviously, one would like to be able to have it work "auto-magically" for Java applets that use HttpSessions. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
