It's transparent to them. Anything that they entered goes into our
"persistent" session info (as text). What we don't do
is shove the EC (and unsaved EO's) in there. Those can be
reconstituted in the other instance much more cheaply than
they can be serialized and transfered. It's a little easier for us
than it is in the general case as we don't have many
sessionful actions and all of the ones that we do have use our own
(custom) workflow. So what we do is effectively
serialize the workflow context and then replay the workflow in the
other instance (up to the point of transfer).
Alan
On Nov 14, 2007, at 2:27 PM, Mike Schrag wrote:
What does it end up looking like to an end-user? My big concern
with this was dealing with backtrack cache ... If someone is in the
middle of filling out, for instance, a multipage form (or anything
that is stateful), when their instance goes down, what was their
experience? I presume it was that you would reload that the
particular user was logged in, but you must have to dump them back
to a main menu or something?
ms
On Nov 14, 2007, at 4:21 PM, Alan Ward wrote:
We did it with memcached. It's not "real" mobile sessions but
it's enough for our purposes. We distinguish
between "persistent" session data and transient stuff. The
persistent stuff goes in an NSDictionary that we
shove into memcached in Session.sleep(). Then in Session.awake()
if we find that we've switched instances
we pull the NSDictionary from memcached and rehydrate the
transient data.
Alan
On Nov 14, 2007, at 2:14 PM, Anjo Krank wrote:
Sound like a job for memcached...
Am 14.11.2007 um 22:08 schrieb Guido Neitzer:
I experimented with that a little bit a while ago and it seemed
just ugly and way too much work for "evening programming". I
ended up with something similar to a dictionary that got
serialized to the database and an id for it in a cookie, but
that was just a simple workaround, not real session management.
It worked quite nice though ...
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-
[EMAIL PROTECTED])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/award%
40apple.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-
[EMAIL PROTECTED])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/mschrag%
40mdimension.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-
[EMAIL PROTECTED])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/award%
40apple.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
