David (enki1...@gmail.com) on 2009-01-10 4:23 PM said: >I'm looking for what I think are some fairly common requirements from >a file copy mechanism. >- simple. Why write something if you can reuse. >- support multi-threading so that you can stay responsive to the UI >while copying large files. >- good error handling. To be able to clearly handle and report errors. >- provides ways to control, ie cancel a large file copy in progress.
In that case, Foundation APIs will not help you. I suggest FSCopyObjectAsync or similar File Manager APIs. There are async options, good error reporting, etc. (The fact that these APIs are 'Carbon' (a vague term anyway) does not mean they are obsolete, a claim you may see sometimes.) Sean _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
