Re: OSX's concurrent tasking
by Bruce Ure at 17:53 17/01/07 (Blogs::Bruce)
I realise about the 2 Move types, but we were clearly dealing with (1), because if we were dealing with (2) the default action would have been move not copy; also it would have been instantaneous and therefore the issues wouldn't have arisen.

So continuing to assume (2), with XP you might get some weirdness like the file being moved might not get deleted after the copy part of the move if someone started using it during that time, and you might get an error dialog telling you this, or something vaguely approximating it, but it wouldn't corrupt it.

Maybe XP just uses (and I don't see why this shouldn't apply to files systems as well as DBMSs) optimistic locking when it comes to moving files around, and OSX pessimistic.

--

<< Ways to while away an hour. Burger King smashed up - video... >>
Powered by
Powered by Novacaster