Session Replication question

[Jess Holle <je...@ptc.com>]

I read the cluster how-to regarding.  I'm still not clear on a couple of 
details if is just using DeltaManager and SimpleTcpCluster:

   1. If useDirtyFlag is false, I assume that the session is entire
      replicated after each and every access.  Is this correct?
   2. If useDirtyFlag is true, are only the pieces of the session that
      were changed (via setAttribute(), removeAttribute(), etc) sent
      throughout the cluster?
          * Or is this a separately configurable option?  If so, when
            one calls setAttribute() and/or removeAttribute multiple
            times on the same attribute during the same request, are the
            duplicate events/deltas coalesced?

I'm just trying to understand the behavior and capabilities of the 
clustering a bit better.  I naively expected to find replication only 
when setAttribute(), removeAttribute() or the like are called /and/ that 
these changes would be coalesced into a minimalistic delta that would 
then be pushed to other nodes in the cluster (with a separate timestamp 
on each attribute if necessary).

--
Jess Holle

Re: Session Replication question

[Filip Hanik - Dev Lists <de...@hanik.com>]

useDirtyFlag is supposed to be the SimpleTcpManager, DeltaManager always 
only replicates deltas. so does the backup manager.
The two managers that work best are DeltaManager and BackupManager, both 
of them replicate upon setAttribute/removeAttribute actions.
DeltaManager replicates to all other nodes in the cluster, BackupManager 
replicates to a single backup node where the data is stored.

SimpleTcpManager, is no longer actively developed.
Filip

Jess Holle wrote:
> I read the cluster how-to regarding.  I'm still not clear on a couple 
> of details if is just using DeltaManager and SimpleTcpCluster:
>
>   1. If useDirtyFlag is false, I assume that the session is entire
>      replicated after each and every access.  Is this correct?
>   2. If useDirtyFlag is true, are only the pieces of the session that
>      were changed (via setAttribute(), removeAttribute(), etc) sent
>      throughout the cluster?
>          * Or is this a separately configurable option?  If so, when
>            one calls setAttribute() and/or removeAttribute multiple
>            times on the same attribute during the same request, are the
>            duplicate events/deltas coalesced?
>
> I'm just trying to understand the behavior and capabilities of the 
> clustering a bit better.  I naively expected to find replication only 
> when setAttribute(), removeAttribute() or the like are called /and/ 
> that these changes would be coalesced into a minimalistic delta that 
> would then be pushed to other nodes in the cluster (with a separate 
> timestamp on each attribute if necessary).
> for the
> -- 
> Jess Holle
>
>



---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org