> If originalContentsURL is supplied, a directory wrapper checks its child
> wrappers against that directory. If a file exists there by the same name and
> with the same modification date, it gets hardlinked, rather than written out
> from scratch.
> Certainly as of 10.8, NSDocument cunningly ma
On 5 Feb 2013, at 10:38, Thomas Zoechling wrote:
>
> Thanks for your response,
>> Given the right conditions, NSFileWrapper can make writing vastly more
>> efficient by writing hard links for unchanged files, rather than recreating
>> them afresh. Have you determined whether this is happening
Thanks for your response,
> Given the right conditions, NSFileWrapper can make writing vastly more
> efficient by writing hard links for unchanged files, rather than recreating
> them afresh. Have you determined whether this is happening at all?
Currently I am trying to figure out what those con
On 30 Jan 2013, at 15:53, Thomas Zoechling wrote:
> Hello,
>
> My NSDocument based app uses packages with the following structure:
>
> - document.package
> +- metadata.plist (small, mutable)
> +- large0.file (large, immutable)
> +- large1.file (large, immutable)
> +- large2.file (large, immuta
Hello,
My NSDocument based app uses packages with the following structure:
- document.package
+- metadata.plist (small, mutable)
+- large0.file (large, immutable)
+- large1.file (large, immutable)
+- large2.file (large, immutable)
While the metadata.plist file can change any time, all large file
