As I was not involved in the design decision, I can not say whether or
not that it is a good call or not. But the reason that we need
application context replication is that the entire site serves up
relatively static data(infrequent updates) to all of it the users. They
did not feel that hitting the DB every time a page is accessed was
efficient.

Rick

Filip Hanik wrote:

>application context data doesn't get replicated, since this is not tied to a
>user, hence it doesn't serve any purpose in fail over.
>ie, what ever got stored in application context on server A, should have got
>stored on B by the same mechanism, not by session replication.
>
>Is there a huge need to replicate context data?
>
>Filip
>
>----- Original Message -----
>From: "Rick Szeto" <rick.szeto@(protected)>
>To: <tomcat-user@(protected)>
>Sent: Monday, January 19, 2004 1:53 PM
>Subject: Clustering question...
>
>
>
>
>>Hi All,
>> I have question about synchronizing data within the application
>>context. If the data of a webapp's application context changes within
>>one of the nodes in the cluster, how does the other nodes get the
>>updated application context data? Is it handle the same way as user
>>session data(via some session manager implementation)? Or does the
>>change(s) get distributed?
>>
>>Thanks for any help you can give,
>>Rick Szeto
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
>>For additional commands, e-mail: tomcat-user-help@(protected)
>>  
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
>For additional commands, e-mail: tomcat-user-help@(protected)
>
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)