dusty wrote:
Creating a separate subsystem on the server to partition a single HTTP session for multiple users and maintain the conversation is classic overengineering. Seems like Seam has gone to a lot of trouble to provide just another way to persist state.
It's not "over-engineering" to allow multiple tabs per user, each having their own state--some applications benefit from this functionality, for several different reasons. I bet if you gave it some thought you'd be able to come up with several trivial examples of when and why you'd need this functionality.
Dave --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
