Talk:Serializing tokens
Add topic | This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||
| ||||||||||||||||||
Speaking of serialization! I just discovered what happens when two people attempt to modify the same Wiki page at the same time!
Yeah, what's that?
Hey, does anyone have any references to criticism of this concurrency model? Anyone in the academia looking into this?
About "Serializing Tokens In Action", I see deadlocks can still happen. So the real difference with mutexes is only the fact that when the thread blocks, the token is released? I think this article is not neutral enough and lacks some counter examination.
JnRouvignac (talk) 07:51, 30 September 2009 (UTC)
If you need to use a technique like this, your code is likely poorly designed from a locking perspective. Components should not call out to other components while holding a lock, and a lock should be held only while touching the specific data that is protected by that lock. It seems that if you need this type of lock, you have too much random code acting under your lock. —Preceding unsigned comment added by 72.49.162.229 (talk) 05:02, 25 May 2010 (UTC)
References
[edit]Archived reference is dead, and the Darwin one is outdated. 98.97.129.24 (talk) 03:02, 6 August 2025 (UTC)