Is it posibile to make a static method of a static class can be make multithreading ?

Question

0.00/5 (No votes)

See more:

C#

multi-threading

Is it possible to make a static method of a static class can be make multithreading ?

Posted 12-Apr-14 0:25am

Tomin James

Add a Solution

2 solutions

Solution 1

Yes - provided the threads don't need to share the same data simultaneously it is possible. You may need to look at the lock statment[^] though.

Posted 12-Apr-14 1:39am

OriginalGriff

Comments

Sergey Alexandrovich Kryukov 12-Apr-14 21:54pm

Well, this is not the only case when, formally, using static properties and fields is possible with thread. Practically, it's a very bad thing. It is not really needed even with thread-shared data and should be best avoided.
—SA

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2014-04-12T15:52:00

Quite possible. Of course it's quite possible. Not only you can use multiple exclusion (lock statements, and the like), you also can use some static members (essentially, properties and fields, as static methods are widely used and don't present problem if they work only on stack).

But this is a very, vary bad idea. Using stack is the way to isolate threads. Static fields and properties are not needed even if you want to share data between threads. Please see my past answer:
Change parameters of thread (producer) after it is started[^],
Making Code Thread Safe[^],
Running exactly one job/thread/process in webservice that will never get terminated (asp.net)[^].

The main idea is: you need to synchronize threads only if they really need to communicate via some shared data or conveyors of data. In other cases, best synchronization is no synchronization. And this comes automatically if you isolate thread data and use more of the stack.

—SA