Re: FW: Application Clustering
Re: FW: Application Clustering
- Subject: Re: FW: Application Clustering
- From: email@hidden
- Date: Wed, 12 Nov 2003 14:21:06 +0000
Hi Jonathan
On Tuesday, November 11, 2003, at 12:31 am,
email@hidden wrote:
There are a couple things to consider.
1) You want to maintain user state outside of the application instance
memory, so it can be restored from another instance even if the
instance
fails. The way to do this would be by writing your own WOSessionStore
that stored the WOSession and everything that came off it in some
external store (db or file system). Theoretically, that's possible,
and
some Apple documentation at least used to suggest this as a
possibility.
Practically.... I think it would require an awful lot of developer
hours
(with the developers behind them being relatively
knowledgable/experienced at WO) to make this work in general for any
component-action based application.
The most challenging part is going to be about the page cache, storing
the page cache externally, and storing all the WOComponents (with
state)
in the page cache externally.
I don't understand that, why do you want to store the WOComponents
present in the page cache?
If the user falls back to another instance, what you need is to
transfer the session data to this instance.
This is done by keeping the data in an external, persistant store that
is not wiped out when the instance fails.
The components can be generated again as needed.
-- Denis.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.