design issues multi threading
-
G'day folks, At the moment I am writing a little application which utilities multi threading to do some processing. Essentially, my application creates a fixed number of threads,i.e. 5. Each thread when started performs three main tasks which represents the operational states the thread is in. The operational state is essentially a particular method that is executed to perform the specific task. In my current design I have created a global array which contains five elements to hold each thread's operational state. Each time the thread moves to a new operational state, the thread's operation state value is changed in the array. I have used the correct locking processes on the array when a thread has to update it. Here is some code which shows I how the thread is started: int []operationalStateArray = new int[5]; void Main(string[] args) { Thread[] ThreadArray = new Thread[5]; MyClass myclass = new MyClass(); myclass.FetchStatusArray(ref operationalStateArray); operationalStateArray [0] = 1; //1 implies encoding task ThreadArray[0] = new Thread(new ThreadStart(myclass.ProcessData)); ThreadArray[0].Start(); ThreadArray[0].Join(); } Having explained my application, my question is that: Is the approach I have taken in accessing the global array using threads is okay or are there better solutions? Is it okay to pass operationalStateArray as a reference to be manipulated by the ProcessData method in MyClass? If anyone can give me their feedback on this I would most appreciate it. cheers Vee
-
G'day folks, At the moment I am writing a little application which utilities multi threading to do some processing. Essentially, my application creates a fixed number of threads,i.e. 5. Each thread when started performs three main tasks which represents the operational states the thread is in. The operational state is essentially a particular method that is executed to perform the specific task. In my current design I have created a global array which contains five elements to hold each thread's operational state. Each time the thread moves to a new operational state, the thread's operation state value is changed in the array. I have used the correct locking processes on the array when a thread has to update it. Here is some code which shows I how the thread is started: int []operationalStateArray = new int[5]; void Main(string[] args) { Thread[] ThreadArray = new Thread[5]; MyClass myclass = new MyClass(); myclass.FetchStatusArray(ref operationalStateArray); operationalStateArray [0] = 1; //1 implies encoding task ThreadArray[0] = new Thread(new ThreadStart(myclass.ProcessData)); ThreadArray[0].Start(); ThreadArray[0].Join(); } Having explained my application, my question is that: Is the approach I have taken in accessing the global array using threads is okay or are there better solutions? Is it okay to pass operationalStateArray as a reference to be manipulated by the ProcessData method in MyClass? If anyone can give me their feedback on this I would most appreciate it. cheers Vee
Hi I think that you can have a class (for example Operation) that has a state property ( a readonly property) that gets the state of the operation. Operation class has a ProcessData method that will be used in ThreadStart to start a thread and within this method the operation can change its state. Using this approach , you can have unlimited operations (not only 5 or a known number of operations) and no one can change the state of a opration except an operation itself that means you don't have to be worry about locking you objects and finally there's no need to remember the index of an external array(when an operation wants to change its state) Good Luck
-
Hi I think that you can have a class (for example Operation) that has a state property ( a readonly property) that gets the state of the operation. Operation class has a ProcessData method that will be used in ThreadStart to start a thread and within this method the operation can change its state. Using this approach , you can have unlimited operations (not only 5 or a known number of operations) and no one can change the state of a opration except an operation itself that means you don't have to be worry about locking you objects and finally there's no need to remember the index of an external array(when an operation wants to change its state) Good Luck