My test show that


Does not lock Storage.pref, and does not prevent Storage.pref from being 
updated in a separate process.

By lock, I mean that during use(Storage) in process A, use(Storage.pref) in 
process B will execute without waiting.

By update I mean that Storage.pref.test can be updated in process B when 
Storage is locked in process A.

I just want to make sure that Storage and it’s shared objects are intended to 
be used this way.

The documentation does not show examples of this.

The point is that locking should occur at the parent of the property being 
updated, not unnecessarily at the top level.

Is that correct?


David Ringsmuth

4D Internet Users Group (4D iNUG)

Reply via email to