read access on a shared object triggers built-in Use/End use. in that sense, the speed "penalty" for access is no different to write.
the speed question really boils down to what you do inside Use/End use. for example, you might do New shared object, New shared collection. you might do collection.query(), collection.map(), collection.reduce(), .push() .reverse(), concat(), etc. each operation on a shared object has a certain cost and you are blocking access during that atomic operation. so to simply measure the speed of locking or unlocking would be missing the point. the same applies to read access. while it is true that you don't need to explicitly Use/End use if you only read a property, it might be necessary to Use/End use for a series of read accesses on multiple properties, to make sure the set of values keep logical integrity. 2018/08/28 0:04、Keith Culotta via 4D_Tech <[email protected]<mailto:[email protected]>>のメール: Does the speed penalty apply to reading values from Storage, or just to writing values to Storage? ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
