Timeline for Waiting for a lock to release with ManualResetEvent and Quartz
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:40 | history | edited | Community Bot |
replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/
|
|
| Oct 1, 2012 at 19:32 | answer | added | tow | timeline score: 5 | |
| Jun 16, 2012 at 1:44 | comment | added | Bill Barry | What version of .NET are you working with? I am asking because 4 provides some new thread primitives which may be of use. | |
| Dec 16, 2011 at 19:53 | comment | added | vgru |
I don't see any benefits in using Quartz.Net vs polling it like you did in the first question. This is a far more complicated way of polling in 1s intervals. I am not sure how your Locker code looks like, but making WaitForLock a member of that class (Locker) would allow it to signal any blocked threads whenever a lock is released. This is probably what Travis had in mind: the purpose of ManualResetEvent is to provide synchronization without polling. You should post your code for the Locker.Lock method, it would be easier.
|
|
| Nov 22, 2011 at 8:42 | history | edited | Bobby | CC BY-SA 3.0 |
Updated with a newer version.
|
| Sep 19, 2011 at 18:59 | history | tweeted | twitter.com/#!/StackCodeReview/status/115862544610099201 | ||
| Aug 16, 2011 at 14:09 | history | edited | Bobby | CC BY-SA 3.0 |
I always get this one wrong.
|
| Jun 29, 2011 at 10:33 | history | asked | Bobby | CC BY-SA 3.0 |