Ben Collins-Sussman <sussman@collab.net> wrote on 04/27/2005 10:39:37 AM:
> On Apr 27, 2005, at 9:29 AM, Mark Phippard wrote:
> >
> > If you have the time and ability, another thing you might try is to
> > see if
> > you can get Dreamweaver to work with the generic Apache mod_dav_fs. If
> > you can, then maybe the Subversion devs can learn something from that?
>
> mod_dav is the "front end" for all dav implementation; it's the thing
> that talks to the DAV client and handles 90% of the logic. The only
> reason autoversioning didn't work very well prior to svn 1.2 was
> because it simply didn't implement the full "provider" API that mod_dav
> expects its backends to handle.
>
> So in *theory*, there should be no difference at all between mod_dav_fs
> and mod_dav_svn now. A client shouldn't be able to tell the
> difference, nor should mod_dav itself.
Couldn't there be a fair number of subtle implementation differences
though? For example, I mentioned previously that Dreamweaver shows the
files as locked, but it shows a lock owner of Unknown. Even though you
followed the spec and provide all that XML junk back to the client, maybe
Dreamweaver doesn't like it? My theory is that Dreamweaver is not even
trying to perform the check-in because it does not think that it owns the
lock. If that is the case, it's UI is pretty bad.
I suspect that the IIS WebDAV implementation was their main testing
target.
I wonder if Julian has any info about Dreamweaver at greenbytes?
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 27 17:39:37 2005