What is the difference between CMutex and CEvent?

Posted on 2008-10-24
Last Modified: 2013-11-20
What is the difference between CMutex and CEvent?
It looks to me that they do the same work.

Question by:UdiRaz
  • 4
  • 3
LVL 16

Expert Comment

ID: 22801726
Both are used in a multi-threaded environment to insure two threads do not attempt to access the same variable at the same time.

A CMutex works by blocking a thread's access to a shared resource while any other thread has access to the shared resource.  You can think of it like this.  A shared resource has one-and-only-one "flag".  A CMutex requests ownership of the "flag", and waits until it's given the "flag".  So basically a thread is attempting to do a job, but a CMutex blocks continued processing until the resource becomes available.

A CEvent works more like an event driven system.  A thread is set up to do some work.  But the thread sits in a wait state doing nothing until another thread, through the CEvent, activates the thread waiting on the CEvent.  So basically, a thread is attempting to do nothing until a CEvent says it's time to do a block of work.
LVL 39

Expert Comment

ID: 22802772
To add to above explanation:

Look at the member functions of CMutex and CEvent.

The CMutex has only Lock and Unlock. So you can write code like

void MyClass::addToMessageQueue(MyMsg msg)

which makes the update of a queue thread-safe in case any access function to the queue has the same lock and unlock. If any of these functions protected by Lock and Unlock was called by a second thread, this second thread waits (automatically) when calling Lock() until the first thread has left the exclusive sequence by calling Unlock.

The CEvent has SetEvent, PulsEvent, ResetEvent and Unlock, which allow a more differentiated usage. You can set an event to signaled (what would release any thread wait for the signal) or reset the signal what would cause any other thread which want get access to the event to wait until it was signaled. The threads would use the CEvent not directly but by means of a CSingleLock or CMultiLock, so for them CMutex has indeed a similar functionality. But from the thread that created the CEvent it is much different.

Author Comment

ID: 22806313
Do Mutex and evrnts work with threads from different process or all thread must be created within the same process?
Announcing the Most Valuable Experts of 2016

MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.

LVL 39

Expert Comment

ID: 22806541
>>>>> all thread must be created within the same process?
a thread is *defined* as one independent subcomponent of one process. So each process has at least one thread (the main thread) and must create its own threads. You can't create a thread and attach it to a different process (beside of writing a new operation system which would allow this).

Author Comment

ID: 22806559
What I ment is can Mutex and/or event synchronize between events from two defference process?

If I will create an even or a mutex with the "Text" in two difference processed?
Will one wait until a second will be reset/unlock?
LVL 39

Expert Comment

ID: 22806815
>>>> If I will create an even or a mutex with the "Text" in two difference processed?
Yes, mutex and events can synchronize between processes cause they are resources managed of the operation system.

There is a 'fast mutex' called CRITICAL_SECTION in Windows. That can be used only within one process and its threads.

Author Comment

ID: 22806825
I DO want to use a synch boject between two different processes !!!

Can I use mutex?
Can I use event?
LVL 39

Accepted Solution

itsmeandnobodyelse earned 500 total points
ID: 22807215
>>>> Can I use mutex?

Yes. You need a named mutex with same name for both processes.

Use the following constructor:

CMutex( BOOL bInitiallyOwn = FALSE, LPCTSTR lpszName = NULL, LPSECURITY_ATTRIBUTES lpsaAttribute = NULL );

for both processes. The bInitiallyOwn tells whether you already want to lock the mutex initially. I would recommend against it.

Note, Windows will use the same internal mutex resource in case a second process use the same name. Hence, you can use it beyond process boundaries.

>>>> Can I use event?

Here the same applies. If used without name it only could be used between threads of one process. If used with name it can be used between processes (and their threads).


Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction: The undo support, implementing a stack. Continuing from the eigth article about sudoku.   We need a mechanism to keep track of the digits entered so as to implement an undo mechanism.  This should be a ‘Last In First Out’ collec…
Exception Handling is in the core of any application that is able to dignify its name. In this article, I'll guide you through the process of writing a DRY (Don't Repeat Yourself) Exception Handling mechanism, using Aspect Oriented Programming.
The viewer will be introduced to the technique of using vectors in C++. The video will cover how to define a vector, store values in the vector and retrieve data from the values stored in the vector.
The viewer will be introduced to the member functions push_back and pop_back of the vector class. The video will teach the difference between the two as well as how to use each one along with its functionality.

837 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question