Databases
StackOverflow2013
Postsdbo
POWhat is a best practice for making a class's properties thread safe?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat is a best practice for making a class's properties thread safe?
    primarykey
    data
    text
    <p>[Edit: It looks like the original question involved a double and not an integer. So I think this question stands if we change the integer to a double.]</p> <p>I have rare issue with reading integer properties from a class used in multiple threads that sometimes returns a zero value. The values are not changed after initialization. </p> <p>This <a href="https://stackoverflow.com/questions/19095042/why-would-an-integer-property-sometimes-return-a-0">question</a> addresses that. The consensus is that even though I'm accessing an integer I need to synchronize the properties. (Some of the original answers have been deleted). I haven't chosen an answer there because I have not resolved my issue yet.</p> <p>So I’ve done some research on this and I’m not sure which of .Net 4’s locking mechanisms to use or if the locks should be outside the class itself.</p> <p>This is what I thought about using:</p> <pre><code> public class ConfigInfo { private readonly object TimerIntervalLocker = new object(); private int _TimerInterval; public int TimerInterval { get { lock (TimerIntervalLocker) { return _TimerInterval; } } } private int _Factor1; public int Factor1 { set { lock (TimerIntervalLocker) { _Factor1 = value; _TimerInterval = _Factor1 * _Factor2; } } get { lock (TimerIntervalLocker) { return _Factor1; } } } private int _Factor2; public int Factor2 { set { lock (TimerIntervalLocker) { _Factor2 = value; _TimerInterval = _Factor1 * _Factor2; } } get { lock (TimerIntervalLocker) { return _Factor2; } } } } </code></pre> <p>But I’ve read that this is horribly slow. </p> <p>Another alternative is to lock the instance of <code>ConfigData</code> on the user side but that seems to be a lot of work. Another alternative I’ve seen is <code>Monitor.Enter</code> and <code>Monitor.Exit</code> but I think Lock is the same thing with less syntax.</p> <blockquote> <p>So what is a best practice for making a class's properties thread safe?</p> </blockquote>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USRich Shealer
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhat is a best practice for making a class's properties thread safe?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhat is a best practice for making a class's properties thread safe?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhat is a best practice for making a class's properties thread safe?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIf you do not mutate state after initialization (initialization being defined as before the class is consumed by other threads) then your code would already be perfectly threadsafe without any locks.
      singulars
      1. POWhat is a best practice for making a class's properties thread safe?
      1. USKirk Woll
    2. COIt is better to develop such design that avoids such situations. I would look into design of the whole thing first.
      singulars
      1. POWhat is a best practice for making a class's properties thread safe?
      1. UST.S.
    3. COThis isn't going to solve the problem you're talking about - as Kirk suggests, your code is *already* threadsafe (based on the sample in your other question, this is definitely the case). I would suggest that you persevere with your first question: the problem is *not* what you suggest it is - your property is not *randomly* returning a zero just because you're accessing it from multiple threads. (From the code you posted, the only way you'd get a zero is if you requested a value before initialisation was complete, but that's a comment for the other question.)
      singulars
      1. POWhat is a best practice for making a class's properties thread safe?
      1. USDan Puzey
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload