Hi,
On 2016-04-19, 7:09 AM, "[email protected] on behalf of OC" <[email protected] on behalf of [email protected]> wrote: >Samuel, > >On 19. 4. 2016, at 15:49, Samuel Pelletier <[email protected]> wrote: > >> WOAllowsConcurrentRequestHandling=NO or YES does not have impact on this >> subject, only the number of live ObjectStoreCoordinator in the app matter. >> >> If you do nat have any external access to the database and a single OSC, you >> are OK. Changes are propagated to others EOEditingContext under the same OSC >> during saveChanges, this is the magic part of EOF. > >Do please correct me if I am wrong, but I believe this does not happen during >saveChanges, but at the end of the R/R loop (or, more precisely, when ECs are >unlocked, which normally is at the end of the loop). Well, it depends. The changes are propagated to all other ECs in the same OSC during save changes. If the EC is not locked, they are processed immediately. If the EC is locked, they are queued for later processing. For ECs associated with this session, that should happen at then of the RR loop. For ECs in other sessions (assuming you are running multi-threaded) that will happen as they are fully unlocked or otherwise need to process these notifications. >Which is why WOAllowsConcurrentRequestHandling has a terrible impact on that. I don’t see why it would. > >As always, of course, I migt be missing something of importance. > >> If a last modified win policy is OK for the updates, you can even disable >> them. The goal of the attributes used for locking is to detect an update >> collision, if you do not care about them, just disable de detection. > >Actually the hypothesis I tried to formulate was more like “if an application >runs one instance and no background tasks, it would work precisely the same -- >be it, depending on the policy, wrong or right -- with or without optimistic >locking of anything but PKs”. Yes, and assuming that no other process will update the database (like you in a SQL tool). Chuck, the wonderpedia > >Thanks and all the best, >OC > >>> Le 19 avr. 2016 à 09:09, OC <[email protected]> a écrit : >>> >>> ... whether I am overlooking something or not. >>> >>> I do think that in a single-instance application with >>> WOAllowsConcurrentRequestHandling=NO and without background tasks is >>> locking of any attribute but PK completely superfluous and can be switched >>> off in the model without any adverse effect. >>> >>> Am I right? Or do I overlook some disaster scenario? >>> >>> Thanks, >>> OC >>> >>> >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Webobjects-dev mailing list ([email protected]) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/webobjects-dev/samuel%40samkar.com >>> >>> This email sent to [email protected] >> > > > _______________________________________________ >Do not post admin requests to the list. They will be ignored. >Webobjects-dev mailing list ([email protected]) >Help/Unsubscribe/Update your Subscription: >https://lists.apple.com/mailman/options/webobjects-dev/chill%40gevityinc.com > >This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
