Re: New FS API, open_path, cloning and dag_node_t

Jim Blandy wrote:

> But otherwise, I think your suggestion is a very good one. The path
> traversal function should simply return a linked list of dag nodes and
> directory entry names. Since we build and use it as part of a single
> trail, we don't need to worry about other processes changing parents
> while we work, so the structure could be very simple. It would help
> write functions like delete,

Believe it or not, delete is exactly what I was working on when I
realized we'll need open_path.

> which want to know that the entry
> actually exists, but only affect the parent. And it provides a
> natural basis for a cloning function.

Exactly. Without this list we'd be traversing the path and opening the
same nodes again all over the place; a waste of time.

-- 
Brane �ibej
    home:   <brane_at_xbc.nu>             http://www.xbc.nu/brane/
    work:   <branko.cibej_at_hermes.si>   http://www.hermes-softlab.com/
     ACM:   <brane_at_acm.org>            http://www.acm.org/