Hmm. I was reading:

Particularly the section under "recovery" which states:

"When Host C restarts, possibly with an upgraded version of Resin, it
needs to use the most up-to-date version of the session; its
file-saved session will probably be obsolete. When a "new" session
arrives, Host C loads the saved session from both the file and from
Host D. It will use the newest session as the current value. Once it's
loaded the "new" session, it will remain consistent as if the server
had never stopped."

So Resin actually implements "have your cake and eat it too" but it's
not working in your case. Perhaps there is some error when the
comparison is made - perhaps the clocks on the two systems are not in
sync. Or something. :)


On 1/8/07, Josh Rehman <[EMAIL PROTECTED]> wrote:
> Corrections below:
> On 1/8/07, Josh Rehman <[EMAIL PROTECTED]> wrote:
> ...
> > While there are [[hacky]] ways to notify the "offline" server of state 
> > changes
> ...
> > How can you have your cake and eat it too? You need some way for nodes
> > to see if they are participating in a distributed session [[on startup]] 
> > and if they
> > are and if there is an active node, ignore any persisted session state
> > and get state from the distributed session. If there is no active
> > node, then load session from disk.
> ...
> Peace,
> Josh

resin-interest mailing list

Reply via email to