Namespace Manipulation: The ability to copy, delete and move resources on the Web server.Ĭollections: The ability to create composite structures for aggregating Web resources.
#C WEBDAV CLIENT UPDATE#
Partial Updating: The ability to update a specified byte range within a resource, minimizing the bandwidth required since the data transmitted is proportional to the size of the change. WebDAV specifies extensions that allow for reading and updating this type of resource. Usually the resource that describes that content, the script itself, remains inaccessible through the server’s namespace.
A page generated by a CGI script is one example. Retrieval of Unprocessed Source: Some Web content accessible through a URL is actually the output of a process. Shared and Exclusive Resource Locking: The ability to serialize updates to the contents of a shared resource. Out-of-line links enable the associations to exist external to the resources themselves, enabling features such as annotation and individual views. Typed Out-of-line Resource Linking: A special type of resource property, typed links is a way of associating resources in terms of semantically meaningful relationships. Resource Properties: The ability to associate arbitrary metadata with a Web resource. The WebDAV working group of the Internet Engineering Task Force is currently developing a specification for extensions to the HTTP 1.1 protocol in the form of new methods, headers, and request and response formats to support a range of new functionality including: However, interoperable, standards-based support is desirable if the World Wide Web is to live up to its original conception as a shared space for collaboration, rather than simply a vast repository for passive browsing. Solutions to this problem exist, ranging from automated publishing based on HTTP PUT, FTP or other mechanisms, to nonstandard locking and versioning extensions. Thus collaboration is limited to those who can share the resources of the local area network or those who are willing to take on the often complex process of managing remote content repositories. In either case, however, the model is one in which the Web serves only as the publication medium, not as the authoring environment and does not directly support truly distributed collaboration in authoring. Reasonable support for collaborative Web development can often be realized in a local area network (LAN) environment, either by deploying existing document management systems or simply by making use of built-in operating system support for LAN-based file sharing. In absence of protocol features to support traditional document management tasks, much of the creation of Web content takes place outside of the Web itself. While the HTTP protocol forms a highly scaleable infrastructure for browsing and searching a distributed set of heterogeneous information repositories, it provides extremely limited support for the authoring and management of that information. We then used that framework to implement a subset of the WebDAV specification to support resource properties, namespace manipulation, and exclusive write locking. Our project was to design a prototype architectural framework for implementing the WebDAV specification as an extension of an existing HTTP server. The WebDAV extensions, proposed in draft form by the WebDAV working group of the Internet Engineering Task Force (IETF), are designed to provide support for traditional document management aspects of collaborative work on the World Wide Web with features like resource properties, namespace manipulation, resource locking, and version control. We have created a working implementation of a server and client that supports a subset of the extensions to HTTP 1.1 for Distributed Authoring and Versioning on the World Wide Web (WebDAV). We will conclude with an analysis of our architecture prototype, an analysis of our extended HTTP server, and describe possible future directions for this project. This document will include sections describing the motivation for this project, the project description, a requirements analysis, and a functional specification.
#C WEBDAV CLIENT CODE#
Step 5: Verifying the WebDAV Servlet Installation *Īppendix B: WebDAV Client Usage Instructions *Īppendix C: Source Code and Documentation *Īppendix D: Class Hierarchy and System Diagrams * Step 4: Configuring the Java Web Server to use the WebDAV Servlet *
0 kommentar(er)
