Timeline for synchronized block - lock more than one object
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 26, 2017 at 15:39 | history | edited | MartyIX | CC BY-SA 3.0 |
deleted 25 characters in body
|
| Feb 24, 2011 at 21:45 | vote | accept | speendo | ||
| Jan 5, 2011 at 19:57 | answer | added | Nicolas Bousquet | timeline score: 27 | |
| Jan 5, 2011 at 18:37 | answer | added | speendo | timeline score: 0 | |
| Jan 5, 2011 at 17:39 | answer | added | Nicolas Bousquet | timeline score: 9 | |
| Jan 5, 2011 at 12:54 | answer | added | mtraut | timeline score: 1 | |
| Jan 5, 2011 at 12:52 | comment | added | Peter Lawrey | Since the operations are very short lived, you may find that using just one global lock performs well enough that you cannot tell the difference. Using one lock might limit yourself to 200K moves per second (is that enough?) but may simplify your code and you won't get a deadlock. | |
| Jan 5, 2011 at 12:37 | answer | added | Péter Török | timeline score: 67 | |
| Jan 5, 2011 at 12:32 | history | asked | speendo | CC BY-SA 2.5 |