David Smith
Michael Tsai
@Catfish_Man What else would you suggest when there are multiple processes accessing the same file?
I’m assuming nobody following me uses NSDistributedLock; if there is, cut it out. I think it’s not deprecated ‘cause we forgot it existed.
-
-
- View other replies
-
.
@mjtsai in ascending order of squickiness: • a database • have one process use XPC to talk to a single writer • defaults • flock() - View other replies
-
@Catfish_Man Those aren't near as convenient as distributed locks with a network filesystem, but I guess that's not common these days. - View other replies
-
@mjtsai NSDistributedLock is a mkdir() spinlock. It’s prone to orphaned locks, doesn’t support donation, and is slow :/ - View other replies
-
@Catfish_Man I'm not using it, and it's pretty clear it would have limitations like that. But seems like a reasonable LCD option to have…
-
-
-
@Catfish_Man Lockfiles are ugly yes, but suggested alternatives? flock / lockf? Use a database? No libdlm-like options, AFAICT -
@HoffmanLabs NSDL uses lock directories actually, heh. I would suggest using a database, or file coordination, or at last resort flock().
-
-
@Catfish_Man please make an NSReaderWriterLock, tho :) -
@Catfish_Man NSDistributedWho?
Stephen Hoffman
Samuel Giddins
Patrick Perini
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.