Re: WOSession serialisation redux
Re: WOSession serialisation redux
- Subject: Re: WOSession serialisation redux
- From: Ramsey Gurley <email@hidden>
- Date: Tue, 19 May 2015 09:23:56 -0700
On May 19, 2015, at 4:03 AM, Paul Hoadley <email@hidden> wrote:
> I’ve had a look at Ramsey’s ERPersistentSessionStorage.framework, and my intention was to create something similar backed by memcached. I got it working to the proof-of-concept level on a trivial app, but using native Java serialisation seems brittle. (By which I mean it falls over pretty fast when you throw a serialisation-based approach into a substantial application.)
I’m curious about the "falls over pretty fast" part. What sort of problems do you have?
I had a few unresolved bugs that could have probably been fixed by rewriting EOEditingContext’s serialization routine, but I never bothered. It became obvious to me that a) nobody was interested in fixing serialization in their legacy classes, and b) everyone was too proud of their one-off direct action workarounds to this particular problem to look at a new solution that works for everything.
Basically I wrote that framework to prove to myself that a component action/D2W app could be used as a “front end” app at scale and do a better job of it to boot. I succeeded in convincing myself that it was possible and left it there :-)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden