Hi, Upon reading the struts 1.0 user guide, I have a question: Isn’t it too expensive to do big session object replication in cluster environment that uses session replication? For example, the user guide suggested using one ActionForm to store all user inputs (from multiple pages, if not whole site). Of course, the form object will be stored in session object. It’s very good to maintain the user inputs. Let’s say that we have a Weblogic cluster environment. The session object will be replicated over the cluster to provide failover service. Big ActionForm inside session object will be more expensive to replicate. In single server environment, big session object is not an issue. It can possibly be a big issue in a cluster that replicates the session objects. As concurrent user session increases, the resources needed for replication of all the session objects will grow much faster, thus slow down the server. Because of this, some people might want to keep the session object as small as possible to reduce the resources needed for replication operations. Of course, those are just “in theory”? Does anyone have any real world experience that uses struts in high volume cluster environment? If so, can you share your experience with the rest of us? Thanks. -Yao Zhu _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
