| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Threads |
MB> Well, I did mention programming complexity for a reason. You end up MB> having to create another mutex semaphore to protect MB> the timer from being reset once it is started, so then MB> you end up with: (1) a mutex semaphore to serialize MB> data insertion into and extraction from the buffer, MB> (2) an event semaphore to signal that data must be MB> extracted from the buffer, (3) a timer started when MB> data is inserted that expires in order to post the MB> event semaphore which signals the need for extraction, MB> and (4) a mutex semaphore to serialize setting and MB> resetting the timer. I was confused about what you were up to, but I think JdeBP cleared it up for me -- you're not using "wait for something" mode, which eliminates step 3 (and therefore 4). Step #2 can be replaced by a WinPostMsg(), if a PM program. Step #2 can be hidden inside of a circular queue, too. --- Maximus/2 3.00* Origin: Sol 3 * Toronto * V.32 * (905)858-8488 (1:259/414) SEEN-BY: 50/99 78/0 270/101 620/243 711/401 409 410 413 430 808 809 934 955 SEEN-BY: 712/407 515 517 628 713/888 800/1 7877/2809 @PATH: 259/414 400 99 250/99 3615/50 396/1 270/101 712/515 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.