|
Hi Chuck, Chuck Hill wrote: I thought that we _always_ need to lock the EOObjectStoreCoordinator and EODatabaseContext even if we have already locked the EOEditingContext because other EOEditingContext's could be accessing the them at the same time on a different Thread. Isn't this correct or is this a special exception to the rule?I thought so. Do you think i need to add locking the EODatabaseContext if i have already locked the EOObjectStoreCoordinator? (I noticed in EODatabaseContextAdditions that you don't) On a side note, I noticed you (or Pierre; i'm not sure who wrote that method) are doing the same thing as i am doing without locking either EOObjectStoreCoordinator or EODatabaseContext in com.webobjects.eoaccess.utilities.Utilities.faultForSupposedPrimaryKeyValue(). Thanks --
Peter Vandoros Software Engineer Etech Group Pty Ltd Level 3/21 Victoria St Melbourne VIC 3000 Australia Ph: +61 3 9639 9677 Fax: +61 3 9639 9577 ---------------------------------- IMPORTANT: This e-mail message and any attachments are confidential and may be privileged. If received in error, please reply to this message and destroy all copies and any attachments. You should check this message and any attachments for viruses or defects. Our liability is limited to resupplying any affected message or attachments. For more information about Etech Group, please visit us at http://www.etechgroup.com.au. |
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
