update a session obj -> setAttribute() -> replication

(Perhaps the most basic coding technique when migrating a servlet to a cluster.)

1st time u call setAttribute(amt, Amount), the container binds Amount obj to the session scope. Subsequent changes to Amount would
be forever visible to any other servlet accessing the same session.

However, in a cluster,

make changes to Amount
setAttribute() again
make changes to Amount
setAttribute() again

I think each method call triggers a session replication.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s