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 ([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]
