The text of this article is not in this database — only its details are. Read it on the old site: Multithreading With .NET
15 Comments
Join the conversation! Your thoughts help the community grow.
Sign in to leave a comment.
The text of this article is not in this database — only its details are. Read it on the old site: Multithreading With .NET
Join the conversation! Your thoughts help the community grow.
Sign in to leave a comment.
Dinesh GabhanePosted Nov 8, 2019, 1:36 AM
Thanks for sharing.
Stan Sainte-RosePosted Jun 23, 2019, 5:02 AM
Hi, thanks for sharing.. a quick question, what would be the best approach for database operations? I have an app using Postgres database and I notice that in multi threading env, I have a lot of opened connections that consumes a lot of memory.. Do you think Semaphore would be a good option?
Nitesh KejriwalPosted Dec 31, 2017, 4:46 AM
Amazing article @Vidya!
Harsh KumarPosted Dec 30, 2017, 12:27 PM
I had almost no idea about multithreading concepts prior to going thru this wonderful article,and now I feel I have started with rt one. Thanks Sir
Prakash TripathiPosted Jun 18, 2016, 5:16 AM
Good one sir. One interjection though, In the line: "Mutex It is used for synchronization between application domains". To my mind, Mutex is used for either across process in an operating system (If named) or across AppDomains within process (If unnamed). Can you plz confirm?
Sr KarthigaPosted May 6, 2016, 9:12 PM
good one sir
NitinPosted May 28, 2015, 1:00 PM
good one
Sibeesh VenuPosted May 28, 2015, 2:19 AM
Good One.
Vidya Vrat AgarwalPosted Jul 3, 2013, 2:27 AM
Sam, I agree. I will edit the article to say so.
Sam HobbsPosted Jul 3, 2013, 2:03 AM
Then you should say so in this article; in other words, this article could say that applications and domains and processes are defined differently for .Net. Or something like that. There have been times that I say in forum posts things like what is said in this article and other developers correct me. I would much prefer to keep things simple but other developers complain when I do.
Vidya Vrat AgarwalPosted Jul 3, 2013, 1:15 AM
Sam, I would say rather making it confusing they made it .NET Specific. Readers can follow http://www.c-sharpcorner.com/UploadFile/84c85b/clr-internals-process-and-application-domain/ to gain background knowledge about Process and Application Domains.
Sam HobbsPosted Jul 2, 2013, 11:16 AM
And if my last comment is confusing for some people then it is because Microsoft has made things very confusing.
Sam HobbsPosted Jul 2, 2013, 11:14 AM
The important point here is that the definition of an application has been made confusing by .Net. In the Windows API, there is one and only one process for each exe file. Unfortunately that is not always true for managed applications. It should also be made clear that that is not done for most managed applications.
Vidya Vrat AgarwalPosted Jul 2, 2013, 3:06 AM
Correct, .NET utilizes memory better than other programming language's runtime. It divides whole process into multiple Application Domians and then run the application inside that.
Sam HobbsPosted Jul 1, 2013, 2:00 PM
Note that in .Net, not every application is in a separate process. There can be multiple Application Domains in one process, correct?