Re: [resolved] Re: really weird move file problem -- bonus points to Jon Hendry
Re: [resolved] Re: really weird move file problem -- bonus points to Jon Hendry
- Subject: Re: [resolved] Re: really weird move file problem -- bonus points to Jon Hendry
- From: Alastair Houghton <email@hidden>
- Date: Tue, 25 Sep 2007 14:21:24 +0100
On 25 Sep 2007, at 00:07, Jaime Magiera wrote:
- Why did my method return before [NSFileHandle closeFile]
finishes? Would control remain in the call until it returns?
It didn't. At least, unless you wrote a load of fancy code to
asynchronously invoke -closeFile.
- What is the caching limit of an NSFileHandle?
There's no such thing. NSFileHandle is a wrapper around a system
file handle. It doesn't have a "caching limit", or any buffering,
except that provided by the system disk cache (which is below the
filesystem, so other processes should be able to access data you've
written almost immediately).
I would think it would be gigabytes. So, why would adding a few
TIFF images take such a long time to close/update?
How large are the TIFF images? What type of disk/filesystem is this
file on? Are you using threading at all in this program? Or are you
using NSFileHandle's asynchronous methods? If so, maybe you have a
race condition of some sort?
Kind regards,
Alastair.
--
http://alastairs-place.net
_______________________________________________
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