RE: svn client accessing current webdav instance

thanks again for the reply, very informative.

i guess where i'm going with the conversation is in
the direction of a doc mgmt system. in other systems
we use versions are part of the regular attributes of
a document stored in the repository.

i used ie web folders as an example client view
of a repository _plus_ version info.

will there be a time when a single dav request will return
a superset of the information provided by webdav and deltav?

so far in my research and this thread it sounds like to achieve
what i want, i would have to maintain two "repositories" one _fs
and one _svn and merge the version data from _svn with the data
from _fs to display to the client.

-or-

i haven't gotten this far yet, but if i implement mod_dav_svn
and point a webdav client (ie)
at a DAV svn location will i see version displayed?

thanks again, you have very helpful greg.

ljk

-----Original Message-----
From: Greg Stein [mailto:gstein@lyra.org]
Sent: Wednesday, February 13, 2002 5:11 PM
To: Knight, Lloyd
Cc: SVN Dev List
Subject: Re: svn client accessing current webdav instance

On Wed, Feb 13, 2002 at 03:55:42PM -0600, Knight, Lloyd wrote:
> thanks much for the reply.
>
> is there any doc on integrating the two?

Integrating which two? The architecture looks something like:

                   _- mod_dav_svn -- Subversion
Apache -- mod_dav /
                  \_
                    - mod_dav_fs -- OS' filesystem

The two mod_dav providers are siblings and define the contents of a given
location in the URL space on a web server. There isn't a way for them to
cooperate because each defines an entirely new/distinct repository for that
content.

> i.e. utilizing the versioning info for a
> generic webdav application? or, does the svn
> module provide all the functionality/data that
> the generic mod_dav does, just accessed differently?

mod_dav_svn is a provider for mod_dav. The provider does not (yet) implement
all of the necessary bits to truly be called a Class 1 server. It also
implements portions of the DeltaV spec, but not completely.

So... for the SVN server to be usable by "a generic webdav application", we
have a bit of work still to do. For 1.0, we'll be a Class 1 server. We'll
wait on DeltaV interoperability until post-1.0.

> envision ie's view of a web folder, along with version
> info for the docs in the folders.

That would require a change in Web Folders itself. We already support
browsing by Web Folders (and other DAV clients), although poorly right now.

> sorry to be such a newbie pest, but i see some great
> potential here and i would just like to solidify my
> understanding of the webdab/deltav worlds.

That potential is exactly why we chose to use WebDAV and DeltaV. We just
aren't as far as we could be (yet).

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org