NSFileManager move/copy to Windows server
NSFileManager move/copy to Windows server
- Subject: NSFileManager move/copy to Windows server
- From: John Gregg <email@hidden>
- Date: Mon, 26 Jul 2004 17:53:35 -0400
Greetings!
I hope someone out there can lend a hand to a fellow propeller-head...
I'm writing a Cocoa app which involves moving/copying files to Windows servers. I implemented NSFileManager for the task, which required me all of 4 lines of code (3 to declare variables and one to call movePath:toPath:handler:).
At first, I ran into a snag when I figured out that the class uses a GUID as a temporary file name, which is 59 characters long. File Services for Macintosh on the Windows server choked, as it STILL only allows for 31 characters via AFP. My co-worker told me to try ExtremeZ-IP, as it has been explored for other implementations within the company. Downloaded the demo, installed, fired it up and it works like a charm!
However, long story short, using ExtremeZ-IP will probably not be an option. [sigh].
So back to the drawing board for John. SMB would be nice alternative, but it doesn't seem to respect the resource fork issue.
Has anyone else experienced this conundrum? Is there a means by which to turn off the GUID being used as a temporary name? (this should most certainly be an option) Or is there a work-around move/copy method that I can borrow or be enlightened to? I'm just nervous of having to address the resource-fork issue manually, which I'd rather not do.
Thanks in advance!
-John
(p.s. Steve, if you're reading this, could you please run it by Bill the next time you have dinner with him? It is definitely one area where Macintosh and Windows do NOT play nice!)
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.