Or if the dirtyFlag is true, only if at least one setAttribute (or removeAttribute) was done on the session that it will get replicated.
use whichever is the easiest and more flexible for you
Jean-Philippe B�langer CGI
John Sidney-Woollett wrote:
Hi
For replication purposes (2 or more tcs in a cluster), how do you let the sessionlistener know to re-replicate your session after you make a change to a property of an object which is bound to the session, but where the session attribute + object iself remains unchanged?
For example, if I bind a (lightweight and serializable) class to the session and change one of its properties, how do I notify Tomcat that I want the session replicated again. Probably as far as TC and the replication code is concerned it doesn't need to do anything because no attribute changes are recorded.
Do I just call session.setAttribute("MyObject", myObject) again (where the myObject reference is the same as before), or do I have to remove and then re-add the attribute? Or is there something that I have missed?
Also, if you add many attributes during a single servlet call, is the replication buffered and delayed until the servlet sends its response, or is the replication attempted each time the session's attributes are changed?
When does anyone think that the recent replication fixes will make it into the next official release?
Thanks for any info.
John Sidney-Woollett
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
