Hi all, I have some query about HTTPSession failover. In a load balanced web server cluster there are different policies to
implement HTTPSession failover. Here is what published at Javaworld. ====== "HttpSession failover allows a client to seamlessly get session information from another server in the cluster when the original server on which the client established a session fails. BEA WebLogic Server implements in-memory replication of session information, while HP Bluestone Total-e-Server utilizes a centralized session server with a backup for HA. SilverStream Application Server and Sybase Enterprise Application Server utilize a centralized database or filesystem that all application servers would read and write to. The main drawback of database/filesystem session persistence centers around limited scalability when storing large or numerous objects in the HttpSession. Every time a user adds an object to the HttpSession, all of the objects in the session are serialized and written to a database or shared filesystem. Most application servers that utilize database session persistence advocate minimal use of the HttpSession to store objects, but this limits your Web application's architecture and design, especially if you are using the HttpSession to store cached user data. Memory-based session persistence stores session information in-memory to a backup server. Two variations of this method exist. The first method writes HttpSession information to a centralized state server. All machines in the cluster write their HttpSession objects to this server. In the second method, each cluster node chooses an arbitrary backup node to store session information in-memory. Each time a user adds an object to the HttpSession, that object alone is serialized and added in-memory to a backup server." ======= My QUERY ----------- Is it possible to implement "distributed web session management" or "Session failover" through JavaSpace technology or other "distributed shared memory area" technology. What is the possibility of this technology in implementing "Local Load balancing" and "Geographic Load balancing" of Web/Application servers. Can somebody through light in this topic, its pros and cons and prefereably give links to some web document on this topic. I do not want reply like "this is container responsibility" TIA soubhratra ____________________________________________________________ Sent via ocsemail from IASRI Intranet System intranet ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
