|
Semaphore Objects
A semaphore object is a synchronization object that maintains a count between zero and a
specified maximum value. The count is decremented each time a thread completes a wait
for the semaphore object and incremented each time a thread releases the
semaphore. When the count reaches zero, no more threads can successfully wait for the
semaphore object state to become signaled. The state of a semaphore is set to
signaled when its count is greater than zero, and nonsignaled when its count is
zero.
The semaphore object is useful in controlling a shared resource that can
support a limited number of users. It acts as a gate that limits the number of
threads sharing the resource to a specified maximum number. For example, an
application might place a limit on the number of windows that it creates. It uses a
semaphore with a maximum count equal to the window limit, decrementing the count
whenever a window is created and incrementing it whenever a window is closed.
The application specifies the semaphore object in call to one of the wait functions before each window is created. When the count is zero indicating that the window limit has been reached the wait function blocks execution of the window-creation code.
A thread uses the CreateSemaphore function to create a semaphore object. The creating thread specifies the
initial count and the maximum value of the count for the object. The initial count
must be neither less than zero nor greater than the maximum value. The creating
thread can also specify a name for the semaphore object. Threads in other
processes can open a handle of an existing semaphore object by specifying its name
in a call to the OpenSemaphore function. For additional information about names for mutex, event, semaphore,
and timer objects, see Interprocess Synchronization.
Each time one of the wait functions returns because the state of a semaphore was set to signaled, the count of
the semaphore is decreased by one. The ReleaseSemaphore function increases a semaphore's count by a specified amount. The count can
never be less than zero or greater than the maximum value.
The initial count of a semaphore is typically set to the maximum value. The
count is then decremented from that level as the protected resource is consumed.
Alternatively, you can create a semaphore with an initial count of zero to
block access to the protected resource while the application is being initialized.
After initialization, you can use ReleaseSemaphore to increment the count to the maximum value.
Threads do not acquire ownership of semaphore objects as they do with mutex
objects. A thread that owns a mutex object can wait repeatedly for the same mutex
object to become signaled without its execution becoming blocked. A thread
that waits repeatedly for the same semaphore object, however, decrements the
semaphore's count each time a wait operation is completed; the thread is blocked
when the count gets to zero. Similarly, only the thread that owns a mutex can
successfully call the ReleaseMutex function, though any thread can use ReleaseSemaphore to increase the count of a semaphore object.
A thread can decrement a semaphore's count more than once by repeatedly
specifying the same semaphore object in calls to any of the wait functions. However, calling one of the multiple-object wait functions with an array
that contains multiple handles of the same semaphore does not result in multiple
decrements.
| Last news from Greatis Software |
 |
|
Nostalgia .Net |
|
.Net is powerful, but not all-powerful, so sometimes we need to use Win32 API for our .Net applications. It's simple enough with Platform Invoke if you have Win32 skill, but we do not always have time to dig the ancient documentation, declare the special types that are compatible with Win32, find the values of the Win32's constants and so on. Nostalgia .Net offers several simple-to-use classes, and components that will allow you to forget about the headache of Win32 and just use the power of Win32 in your application the same way as you use the native. Net classes. More » |
| Recommended software for developers |
 |
|
Ultimate Pack |
|
Component pack for Delphi and C++ Builder that contains runtime form designer, runtime object inspector, print suite and much more for the very special price. More » |
 |
|
Form Designer .Net |
|
Unique runtime form design solution that allows to edit any form in .Net WinForms application at runtime with full source codes for only 300 euro! More » |
 |
|
Print Suite .Net |
|
Print Suite .Net is a set of components for easy printing texts, images and grids from your WinForms applications. Full C# source codes are available More » |
 |
|
Gradient Controls .Net |
|
Gradient Controls .Net offers controls with gradient background feature. Labels, panels and so on... Full C# source codes are available More » |
 |
|
Greatis iGrid |
|
iGrid plots drawing grid right over your desktop, so you can use it everywhere, with any drawing application without any special plugins for different graphic editors. More » |
All the contacts and projectsDmitry Vasiliev (just.dmitry)
Related LinksSoftware for Visual Studio .NET developers Software for Delphi and C++ Builder developers Software for Visual Basic 6 developers Delphi Tips&Tricks MegaDetailed.NET More Online Helps Win32 Programmer's Reference Win32 Multimedia Programmer's Reference OLE Programmer's Reference Microsoft Windows Pen API Programmer's Reference Microsoft Windows Sockets 2 Reference Microsoft Windows Telephony API (TAPI) Programmer's Reference Unix Manual Pages
|