• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: How do I get a file reference w/o relying on the path?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How do I get a file reference w/o relying on the path?


  • Subject: Re: How do I get a file reference w/o relying on the path?
  • From: Jens Alfke <email@hidden>
  • Date: Sun, 4 Apr 2010 10:50:50 -0700

You're saying that if I have a FSRef to a file, then the file is moved, the FSRef will still reference the moved file and not the location where it used to be?

That's surprising to me, because FSRefs were created as a replacement for FSSpecs, which do not have that property (they were a struct {volume ID, dir ID, filename}.)

Anyway, note that a file inode ID is more fragile than an alias/bookmark, because it won't survive the common practice of replacing an old copy of a file with a new one ("safe save") unless the code doing the replace is careful to propagate metadata to the new file.

--Jens {via iPad}

On Apr 4, 2010, at 8:00 AM, Ken Thomases <email@hidden> wrote:

> On Apr 3, 2010, at 8:31 PM, Jens Alfke wrote:
>
>> Ken, he asked for a reference that wouldn't break if the file were moved or renamed. Neither FSrefs nor URLs have that property.
>
> Yes, they do.
>
> From the link I gave <http://developer.apple.com/mac/library/documentation/cocoa/conceptual/LowLevelFileMgmt/Articles/FileManagementNSURL.html>:
>
> "File reference URLs provide a way to track a file by its ID. This means that the reference is valid even if the file’s name or location in the file system changes."
>
> File reference URLs are new with Snow Leopard.  Check out the release notes and "What's New in Mac OS X: Mac OS X 10.6" to learn about them.
>
> And FSRefs have always had this property.  Adding file reference URLs was essentially a way of allowing URLs to provide analogous functionality as FSRefs.
>
> Regards,
> Ken
>
_______________________________________________

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

  • Follow-Ups:
    • Re: How do I get a file reference w/o relying on the path?
      • From: Jean-Daniel Dupas <email@hidden>
    • Re: How do I get a file reference w/o relying on the path?
      • From: Charles Srstka <email@hidden>
    • Re: How do I get a file reference w/o relying on the path?
      • From: Ken Thomases <email@hidden>
References: 
 >How do I get a file reference w/o relying on the path? (From: Brad Stone <email@hidden>)
 >Re: How do I get a file reference w/o relying on the path? (From: Ken Thomases <email@hidden>)
 >Re: How do I get a file reference w/o relying on the path? (From: Jens Alfke <email@hidden>)
 >Re: How do I get a file reference w/o relying on the path? (From: Ken Thomases <email@hidden>)

  • Prev by Date: Re: How do I get a file reference w/o relying on the path?
  • Next by Date: Re: How do I get a file reference w/o relying on the path?
  • Previous by thread: Re: How do I get a file reference w/o relying on the path?
  • Next by thread: Re: How do I get a file reference w/o relying on the path?
  • Index(es):
    • Date
    • Thread