This article discusses WebDAV, which has become an important communication protocol for the Web as an extension to HTTP 1.1. It describes what WebDAV is and how it could be useful in your client/server architecture.

This document explains how to set up and use the beta version of the eZ WebDAV content administration sub-system. The functionality described here is new and will appear in eZ publish 3.2 (also in beta releases).

WebDAV stands for "Web-based Distributed Authoring and Versioning". It is a set of extensions to the HTTP protocol which allows users to collaboratively edit and manage files on remote web servers.

This TechNote offers several suggestions for troubleshooting a failed WebDAV connection. Because of the many factors that can cause a WebDAV connection failure, however, you may need additional assistance after trying the four suggestions below.

Slide includes a full featured command-line based WebDAV client, which allows full access to the Slide server using the WebDAV protocol. Although the client is part of the Slide project, it is not tied to the Slide server, and was proven to be interoperable with a wide variety of WebDAV servers from other vendors. The reason why it is part of Slide instead of being fully independent and developed separately is the need to manitain a consistent feature set between the client and the server. For example, if ACL support is added to the server, we will want to also have ACL support in the client to be able to manipulate the ACLs.

WebDAV, web-based distributed authoring and versioning, is a convenient replacement for FTP when developing web sites. Many editing tools can save to a WebDAV server directly and several operating systems can provide a filesystem to a WebDAV server.

It is at this point fairly common in the Zope world to use WebDAV to connect to a Zope application server for remote editing. It is also at this point fairly confusing to those new to Zope how to connect to it using WYSIWYG web design tools. As these tools are becoming more and more advanced in their ability to deal with web application development, they constantly become better for use with building Zope websites and applications. This Article is aimed at web designers/developers who have a basic understanding of Dreamweaver, and want to simply connect to a Zope. It does not at all attempt to get into any sort of development using Zope, aside from connecting to a Zope instance. Though screenshots were taken from DreamweaverMX running on MacOSX, the instructions should directly apply to Windows users as well.

WebCT 3.8 supports WebDAV for site designers. WebDAV stands for "Web-based Distributed Authoring and Versioning." It allows users to edit and manage files on remote web servers using a drag-and-drop interface. This means you can now manage your WebCT files almost as easily as managing files on your own computer.

This functionality is currently under development. It will hopefully appear in eZ publish 3.2. Most of it will be available from within trunk [as soon as it reaches an alpha/usable state]. eZ WebDAV is a WebDAV server abstraction library. It enables you to quickly develop WebDAV enabled PHP servers/applications.

Work through the following troubleshooting procedures to help establish a connection. If you need help with them, consult your system administrator.

Managing your uploaded files with WebCT's File Manager has always been a slow process due to the Web browser's limitation of being able to handle just one file at a time. WebDAV overcomes this limitation and makes managing your WebCT files as easy as dragging your files from one folder to another.

X-Hive Corporation, leading innovator in XML database technology announced today that it has added support for WebDAV, J2EE, and XUpdate to the latest release of its native XML database, X-Hive/DB 2.0. By introducing these new modules, X-Hive continues to provide XML and Java developers with support for mission critical native XML database applications.

WebDAV is a set of extensions to HTTP/1.1 that allows clients to perform remove web authoring operations [3]. Of these extensions overwrite protection by locking, name-space management and properties (metadata) are fully implemented. Other proposed extensions include version management, advanced collections and access control with HTTP Digest Authentication. XML is used to encode method parameters and responses.

In the first session of the XML DevCon Fall 2000 conference, Greg Stein delivered an introduction to WebDAV, the Web Distributed Authoring and Versioning protocol. Stein is an open source developer working with WebDAV and Python -- he is the author of the mod_dav Apache DAV support, soon to be an integral part of Apache 2.0.

This document explains how to set up and use the beta version of the eZ WebDAV content administration sub-system. The functionality described here is new and will appear in eZ publish 3.2 (also in beta releases).

WebDAV (World Wide Web Distributed Authoring and Versioning) is the Internet Engineering Task Force (IETF) standard for collaborative authoring on the Web: a set of extensions to the Hypertext Transfer Protocol (HTTP) that facilitates collaborative editing and file management between users located remotely from each other on the Internet.

Web-based Distributed Authoring and Versioning (WebDAV) is a standardized, platform-independent set of extensions to HTTP 1.1 that allows users to collaborate over the Internet by editing and managing files remotely.

The WebDAV component implements an easy-to-use interface to the Web Distributed Authoring and Versioning protocol (WebDAV). The component allows remote management of resource properties and collections, including creation, deletion, listing, copying, and moving. Resource locking is also supported.

One of my personal background tasks in the last couple of months has been finding sample applications to excercise Tarawa with. Although my load is high and I've only got a single processor - me - I'm still trying to push this.

Today the typical use of the World Wide Web is to browse information in a largely readonly manner. However, this was not the original conception of the Web; as early as 1990, a prototype Web editor and browser was operational on the Next platform, demonstrating how Web content could be read and written. Unfortunately, most of the world never saw this editor/browser, instead developing their view of the Web from the widely distributed text-based line mode browser. When NCSA Mosaic was developed, it improved the line mode browser by adding a graphical user interface and inline images, but had no provision for editing. As Mosaic 2.4 reached critical mass in 1993-4, “publish/browse” became the dominant model for the Web.