Re: Write with NSFileWrapper vs. copy with NSFileManager
Re: Write with NSFileWrapper vs. copy with NSFileManager
- Subject: Re: Write with NSFileWrapper vs. copy with NSFileManager
- From: Mike Abdullah <email@hidden>
- Date: Wed, 26 Mar 2014 10:16:45 +0000
On 26 Mar 2014, at 10:13, Colas B <email@hidden> wrote:
>
> Yes indeed,
>
> I'm using this method to manage additional data in a document.
> Want you say Mike frightens me a little bit, I would not want all my memory used my extra files when I save the document.
>
> Which options should I use if I want the file wrapper to read/write as less as possible when I update this additional data on the disk? Is there a special procedure to follow if I want to remove a file from the additional data on the disk?
>
If you’re writing a directory (package), and pass in a suitable original URL, NSFileWrapper will do its best to write hard links for any files it detects haven’t changed.
I should probably point out that NSFileWrapper can be configured to use memory mapping, which may lower the memory requirements for your app.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden