Virtual Developer Workshop: Containerized Development with Docker
When a program is using more then one thread, there will be in most cases the need of synchronizing the data. This can be 'easily' done by using one of the provided synchronization classes of MFC: CMutex, CSemaphore, CEvent, CCriticalSection. In some of the simple cases these classes are everything one needs to implement the desired syncronisation between all treads.
To obtain access to a locked resource you have to use a CSingleLock or CMultiLock object. These objects have a simple interface. Either you are granted access to the data or you don't. But sometimes we need a more complex locking mechanism and then we are left in the blue. I needed a mechanisme that could be called something like this : 'Single-Write, Multiple-Read, Write-Has-Priority-To-Read'.
Multiple-read means that multiple threads are granted access to read the data at the same time. A request to edit the data will blocked, requests to read will be granted access.
>Write-Has-Priority-To-Read means that when a request to edit the data is done, while the data is locked, the calling thread waits until the reading thread(s) are finnished. When there are new requests to read the data after the 'write-request' is done the threads are blocked until the writing-operation is finneshed, eventhough the write-thread is still waiting until he is granted access to the data.
To create this behaviour I create my own locking object. This encloses a CMutex and two CEvents. The CMutex is used to control the internal data. The two events are used to signal a write-thread or some read-thread that the access to the data is granted. This object is has alsoo a simple interface to control the data:
- void StartReading();
- void StopReading();
... lock.StartReading (); // we have access now ... lock.StopReading ();
- BOOL StartWriting();
- void StopWriting();
When two threads launch a request for edit the data only one thread may be granted access. The request of the other thread is denied. The 'StartWriting' function returns whether the request is accepted or not. Usign a loop it is possible to allow multiple threads requesting a write-operation.
while (!lock.StartWriting) Sleep (100); // wait a little while // we have access now ... lock.StopWriting ();