CDV ❯ Throw exception on unlocked read
-
New Feature
-
Status: Open
-
3 Minor
-
Resolution:
-
DSO:L1
-
-
prodmgmt
-
Reporter:
-
September 07, 2007
-
0
-
Watchers: 1
-
March 19, 2010
-
Description
I don’t have a *strong* opinion about it, but some people get confused at the asymmetry between our exception throwing policy: we throw an exception when you try to mutate a shared object without a shared lock, but we don’t throw an exception when you try to read a shared object without a shared lock. Perhaps we should make this behavior symmetrical.
Comments
Tim Eck 2007-09-07
Taylor Gautier 2007-09-11
We should add this and make it optional - as well as allow writes to be optional (according w/Steve).
Fiona OShea 2007-10-26
WE need to add design for this default settings turn it on/off eclipse plugin integration
Saravanan Subbiah 2007-10-30
This could have a big performance impact.
I’m not really in favor of it, but another way of making it symmertrical would be not throw exceptions on writes. I guess this would effectively mean that we could commit these writes whenever we saw fit.