> What I have done is to use a lock across the work of handling R-R cycles and > the change notification (the only place where the invalidate is actioned). > In this way, if the issue is one of concurrency with "regular EC use" then I > should see this issue go away for human-facing instances which are doing any > EC-work outside of the R-R cycles. It's still a fair way off a production > deploy, but I will let you know if this resolves the issue. in wonder's we take a dbc lock during the background queue processing, then do a refreshing fetch of the affected EO so that it updated the snapshots. you really don't want to ever do an .invalidate() because if you any EO's in an modified state, they'll be messed up.
ms _______________________________________________ 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 arch...@mail-archive.com
