On May 23, 2014, at 6:52 AM, Matthew LeRoy wrote:
> ...and come up with a way to handle the scenario where
> multiple users have the same file open.
It's called client/server. Anything less is a dangerous kludge. (If you *knew*
your file system had some kind of proper locking support, then it c
On 5/22/14, 12:21 PM, "Jens Alfke" wrote:
>If you implement the lower-level read/write methods in NSDocument, you
>have full control over opening and closing the file. You can then make
>whatever filesystem calls you want to lock/unlock it.
You¹re talking about readFromURL:ofType:error:, yes? A
On May 22, 2014, at 9:44 AM, Gary L. Wade wrote:
> I've only just run across this as a potential solution to a prospective need,
> but might Kernel Authorizations be what you need?
> https://developer.apple.com/library/mac/technotes/tn2127/_index.html
Only if you’re implementing your own files
I've only just run across this as a potential solution to a prospective need,
but might Kernel Authorizations be what you need?
https://developer.apple.com/library/mac/technotes/tn2127/_index.html
--
Gary L. Wade (Sent from my iPhone)
http://www.garywade.com/
> On May 22, 2014, at 9:21 AM, Jens
On May 22, 2014, at 8:51 AM, Matthew LeRoy wrote:
> Does anyone have any idea if there is a way to get the document architecture
> to lock a document file when it is opened?
If you implement the lower-level read/write methods in NSDocument, you have
full control over opening and closing the f
Good morning,
Does anyone have any idea if there is a way to get the document architecture to
lock a document file when it is opened? When I say “lock”, I’m talking about an
exclusive file lock at the filesystem level, as in no other user or process can
open, move, or delete the file. I’m not t
