This book is divided into five main sections. Introductory MaterialChapter 1, Introduction, introduces WebDAV, and why and how it was developed. Chapter 2, History of Web and Collaborative Authoring, gives more depth on the technologies that existed prior to WebDAV (FTP, HTTP), and the drawbacks that the WebDAV designers knew they needed to overcome. Chapter 3, HTTP Mechanics, provides a review of HTTP that is only necessary if you're not already familiar with HTTP. How WebDAV WorksChapter 4, Data Model, provides an overview of WebDAV functionality by explaining the data model, which is crucial to understanding how WebDAV works. Chapter 5, WebDAV Modifications to HTTP, explains how WebDAV extends HTTP methods. Chapters 6, 7, and 8 describe the practical aspects of how the core WebDAV protocol works. These chapters will be useful to developers of WebDAV-enabled software and custom applications. Chapter 9, Putting the Pieces Together, pulls this material together into extended examples. WebDAV ExtensionsChapter 11, Versioning, and Chapter 12, Multifile Versioning, introduce the WebDAV versioning standard DeltaV in sufficient depth to enable the reader to read the DeltaV specifications and be able to put details into context. Chapter 13, Access Control, introduces the Access Control specification, which is soon to be a standard. Software and Custom ApplicationsChapter 10, WebDAV Products and Tools, introduces a number of client and server software packages that support WebDAV. Chapter 14, Custom WebDAV Applications, and Chapter 15, Designing WebDAV Applications, discuss what custom applications can do with WebDAV, and how to design such custom applications. Reference AppendixesMicrosoft and Windows Tips and HTTP Status Codes. Typographical ConventionsIn this book, certain fonts and character types are used to set off certain kinds of words. Here are the conventions and an example of each:
Icons UsedThree icons are used to draw the reader's attention to various sections.
ReferencesMany of the references in this book are in a standard recognizable style including the primary author's last name and year of publication: [Stevens98] However, I use an odd reference style for IETF standards, because those standards are more commonly known by their IDs or names than by their authors or dates. IETF standards are each issued a Request for Comments (RFC) number: [RFC2518] This approach is intended to give the reader a quick idea whether the reference is a protocol standard or some other document. |