On 1. Mar, 2010, at 00:43 , Timo Hoepfner wrote: > Please don't get me wrong, but I'm still under the impression that you're > just fighting symptoms, not the root cause of the problem.
I really have to agree here. I had a similar system set up for a long time and it was using a single database instance and added a "client" relationship to every row inserted. Then, in awakeFromFetch objects "exploded" if their client didn't match the client of the current session / RR loop. When I wrote that, I decided it's better to show an error page (and sending me a trace) in such a case then fetching data from a different client to the user's session. Worked out really well. And as I was still able to scale horizontally with giving different clients different subdomains to work on (clientname.service.com), we never had problems with high traffic customers - they got on their own box if they paid enough (or were throttled). cug _______________________________________________ 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]
