monitor

When is it appropriate to use either the Monitor class or the lock keyword for thread safety in C#? EDIT: It seems from the answers so far that lock is short hand for a series of calls to the Monitor class. What exactly is the lock call short-hand for? Or more explicitly, class LockVsMonitor { private readonly object LockObject = new object(); public void DoThreadSafeSomethingWithLock(Action action) { lock (LockObject) { action.Invoke(); } } public void DoThreadSafeSomethingWithMonitor(Action action) { // What goes here ? } } Update Thank you all for your help : I have posted a another

What's a monitor referred to in concurrent programming in Java? When I read that "every object has associated a monitor" what does it meaning? Is it a special object? A monitor is mechanism to control concurrent access to an object. This allows you to do: Thread 1: public void a() { synchronized(someObject) { // do something (1) } } Thread 2: public void b() { synchronized(someObject) { // do something else (2) } } This prevents Threads 1 and 2 accessing the monitored (synchronized) section at the same time. One will start, and monitor will prevent the other from accessing the region before

For mastering of some technology you have to know how it's made at one abstraction level lower. In case of multithreading programming, it will be good to know about synchronization primitives. Here is the question, how implemented Lock (Monitor) in .NET? I'm intrested in such points: - does it utilize OS objects?; - does it require user mode or kernel mode?; - what is overhead for threads that are waiting for lock?; - in what cases threads queue that awaiting for the lock could be violated?. Updated: "If more than one thread contends the lock, they are queued on a “ready queue” and granted the

Is there any way to start/lunch a program through Process in another screen? Someone asked that here but there was no answer. Note: it is not a form in my app, I'm asking about running an external program in another screen! Since the window is not yours, you can only move it by invoking the Windows API. You will have to do this: Launch the process. Use FindWindow to retrieve the handle to the window. If the window doesn’t exist yet, the process hasn’t created it yet; sleep for 500ms and then try again. (But don’t go into an infinite loop; stop if you can’t find the window after a reasonable