Re: FS API requests

On Sun, Nov 26, 2000 at 05:06:26PM -0500, Jim Blandy wrote:
> Greg Stein <gstein@lyra.org> writes:
> > Some random requests for the FS API:
> >
> > *) svn_fs_dirent_t returns an svn_fs_id_t for a node. It would be nice to be
> > able to use that for opening the child node (rather than path
> > construction, and making the FS do the path->node mapping)
>...
> ... no, that won't work because ...

Ah. Gotcha... that makes a lot of sense. Never mind, then :-)

[ good thing they're requests rather than demands :-) ]

>...
> > *) there are two properties that DAV needs:
> >
> > - creation date (when was the resource created)
> > - last modified date (for this revision)
> >
> > Will the FS track either/both of these (and provide an API), or should I
> > (manually) keep these in a property?
>
> If the FS does provide an API, it'll just be a layer on top of the
> properties. So it doesn't make much difference either way.

Okay. I'll drop in some pseudo-code to fill out these things, then we can
plug in the "real thing" later.

Note that the above properties are "read only", so they are *quite* like
other properties.

> > *) still need the "latest revision" API that I can pass to svn_fs_open_root
>
> Sorry. Will provide soon.

No time pressure, just a friendly reminder that I'll need it at some point.

> > That's it for now :-) ... more if/when I find them.
>
> Keep 'em coming!

:-)

There will probably be quite a few when I get to the "reporting" part. That
is where I need to query stuff like "is there any difference between <this>
revision and <that> revision?" Or "is <this> revision of file <xyz> up to
date?"

Not sure what the specific demands are yet. I also need to review/revise the
webdav-usage document for some recent changes in DeltaV. I doubt that I'll
have a firm grasp until I dig in and write code, though. Too many variables
at unknowns right now.

Thanks!

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/