W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2000

RE: Source: header

From: Kevin Wiggen <wiggs@wiggenout.com>
Date: Tue, 19 Dec 2000 15:37:19 -0800
To: "John Stracke" <francis@ecal.com>, <w3c-dist-auth@w3.org>
Message-ID: <ONEOJMKKAIDAGPLOPJEDIEEMCKAA.wiggs@wiggenout.com>

There are instances when a user would like to get a file from a URL (mp3,
word doc, etc) that is not on a Webdav Server (or one that does not allow
for cross server Copies).  This allows Xythos to go get the file and store
it for the user.

There are a lot of proprietary extensions out there to do "cross loading"
Xythos would like to see a Webdav COPY be the standard, thus we propose
adding the "Source" tag so that clients can cause server-server copies
across Webdav Servers and/or across a Webdav Server and a HTTP server.

This gives flexibility to a Webdav server as it is able to copy resources
between machines both as a Source and a Destination.


-----Original Message-----
From: w3c-dist-auth-request@w3.org
[mailto:w3c-dist-auth-request@w3.org]On Behalf Of John Stracke
Sent: Tuesday, December 19, 2000 5:57 AM
To: w3c-dist-auth@w3.org
Subject: Re: Source: header

Keith Wannamaker wrote:

> Recently I worked to add support to Xythos Storage Server for
> remote COPY destinations.  To maximize flexibility, Xythos goes
> a step farther and adds support for a "Source:" header.
> It is hoped the group might consider adding this header to a
> future revision of RFC 2518.

Um...why? What does it add that you can't express with Destination:?

|John Stracke    | http://www.ecal.com |My opinions are my own. |
|Chief Scientist |==============================================|
|eCal Corp.      |If you choke a Smurf, what color does it turn?|
|francis@ecal.com|                                              |
Received on Tuesday, 19 December 2000 18:37:10 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:22 UTC