This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Can anyone comment as to how application servers traditionally maintain state? Is it something as simple as some in memory Map instance associating a key with perhaps another Map? And if so, what about distributed sessions...I guess either a central in-memory mechanism maintaining state across all servers in a cluster (a database even)? Just curious as to whether or not anyone out there has been on a team *writing* an application server and how state was managed. Thanks, Cory