Its been a while since I first tried using WebDAV but I tried it with Dreamweaver and MS's WEB Folder version and I can't remember if one or both did this. I could download and upload the files fine except that downloading would download the rendered source and not the true source. So in that case since we use a tag like <dtml-var topbanner> on all our pages then editing the rendered source would eliminate that and all dtml tags which would make that page not update when the topbanner object gets changed. It seems that I recall seeing some discussion somewhere that type of incident may have been client specific and some download rendered source and some true source. But being http based and "REQUEST/RESPONSE" I can see why this might happen. This was with : Zope Version (Zope 2.6.1 (binary release, python 2.1, linux2-x86), python 2.1.3, linux2) Python Version 2.1.3 (#1, Sep 19 2002, 13:15:46) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] System Platform linux2 Thomas On Wed, 17 Mar 2004 18:01:06 -0600, J. Cameron Cooper <jccooper@jcameroncooper.com> wrote:
Paul Browning wrote:
--On 17 March 2004 15:33 +0000 John Poltorak <jp@warpix.org> wrote:
I'm still trying to work out how WEBDAV differs from an FTP filesystem driver...
Here's two differences:
1. File locking (that's the DA bit - Distributed Authoring - you don't stomp on other people's stuff).
2. Easily secured over SSL (no passwords in the clear)
3. Increasingly ftp is blocked at firewalls
Others are likely to extend this list ....
WebDAV is an extension to the HTTP protocol, and thus is REQUEST/RESPONSE based unlike FTP. (This can be more efficientalso allows it to be sneaky wrt firewalls.)
A regular HTTP resource also maps to a WebDAV resource more directly than FTP.
There's more, but you're right that they basically provide the same sort of service. Note that Zope treats them similarly.
See also:
http://webdav.org/other/faq.html
--jcc
-- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/