Comments on: lokc – a distributed locking framework in Java http://v1.ripper234.com/p/lokc-a-distributed-locking-framework-in-java/ Stuff Ron Gross Finds Interesting Sun, 02 Aug 2015 11:03:35 +0000 hourly 1 https://wordpress.org/?v=4.5.3 By: ripper234 http://v1.ripper234.com/p/lokc-a-distributed-locking-framework-in-java/comment-page-1/#comment-1498 Sun, 05 Jul 2009 07:45:03 +0000 http://v1.ripper234.com/?p=1086#comment-1498 Shlomo – yes, something like that. I do need auto-release semantics – after X time the lock should be released automatically.

I don’t think I’ll write an SQL implementation, the implementation in GigaSpaces was rather easy and good enough for us – most of the time was spent on writing the tests anyway.

]]> By: Shlomo http://v1.ripper234.com/p/lokc-a-distributed-locking-framework-in-java/comment-page-1/#comment-1497 Sun, 05 Jul 2009 07:39:35 +0000 http://v1.ripper234.com/?p=1086#comment-1497 I have no idea what the library does, but I shamelessly assume that by saying “using MySQL” you’re referring to creating some table holding the lock data, in a similar way to Gigaspaces.
FYI, MySQL has support for application locks in the form of RELEASE_LOCK() and GET_LOCK(). Those are just named mutexes you can create, without meddling with tables. More info here: http://dev.mysql.com/doc/refman/5.1/en/miscellaneous-functions.html. Those functions are pretty neat and sometimes very convenient, but I don’t know if they are any good for you.

]]> By: ripper234 http://v1.ripper234.com/p/lokc-a-distributed-locking-framework-in-java/comment-page-1/#comment-1496 Sun, 05 Jul 2009 06:08:57 +0000 http://v1.ripper234.com/?p=1086#comment-1496 Thanks, I pondered the name for some time.

]]> By: Avish http://v1.ripper234.com/p/lokc-a-distributed-locking-framework-in-java/comment-page-1/#comment-1495 Sat, 04 Jul 2009 20:34:24 +0000 http://v1.ripper234.com/?p=1086#comment-1495 Nice to see us you contributing to the community. Way to go! Also, good choice of name.

]]>