Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I normally see it as a version column in a database where it being with the data makes it non-distributed.

I'm not even sure how it could be used for exclusive update to a resource elsewhere--all clients will think they 'have' the lock and change the resource, then find out they didn't when they update the lock. Or if they bump the lock first, another client could immediately 'have' the lock too.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: