Re: File level action protocol
Re: File level action protocol
- Subject: Re: File level action protocol
- From: Thomas Tempelmann <email@hidden>
- Date: Sat, 9 Jul 2005 09:50:45 +0200
Mike,
>How much work do you plan to do on each notification? Do you need to
>know about each and every operation as it happens, or is it enough
>for you know that the file has been modified at some point prior to
>"now"?
The latter is enough.
>If the delayed notification is acceptable, how long a delay can you
>tolerate?
Several seconds are no problem.
Goal is to be able to tell the _user_ eventually what files have
changed on his computer without having to scan the entire directory
tree and compare it to a previously saved tree.
>What about your other users? Is it important that it only be files
>that a specific user can see?
I like to know about all changed files that are present on a disk,
including system files.
>lookup passes a parent object and a name fragment to a
>filesystem and gets back a child object or an error.
You can also look up by a file ID instead of parID+name, right?
So, all I need is to know a file's ID for my project.
>Lookups performed by fileid may not have a meaningful parent
>identifier at all
On HFS+, they do, and that's all I care about.
As long as I can learn the File ID while I do the recording, I should
be fine.
>The file handle is not relevant at the layer you're interested in;
>it's a per-process association between a descriptor number and a vnode.
So, what I need then is a (later) association between a vnode and a
File ID.
Isn't the Vnode identified by a unique number that is, like the dir
and file ID, remaining constant as long as its file/dir exists? Can
I record this vnode number when I get a "file change" notification?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden