Hello Anjo;
Yes this can be quite annoying -- the user gets a session timeout. I
guess the problem is that beyond the instance number in the path, the
adaptor doesn't know there is or is not a session.
cheers.
before proceeding. Now, the problem is that there may several
reasons for 20 not to reply, but now instance 10 has no way of
knowing that the session that doesn't exist in it's own session
store didn't really expire but comes from a temporarily unavailable
instance 20. Does anyone have enough inside into the adaptors to say
why the request is rewritten? It looks pretty dumb to me, but maybe
there is a good reason... I think if should store the old request
add at least a header to indicate that this is not the intended
instance.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
