- From: Roy T. Fielding <fielding@kiwi.ics.uci.edu>
- Date: Mon, 21 Sep 1998 14:37:13 -0700
- To: John Stracke <francis@netscape.com>
- cc: WebDAV WG <w3c-dist-auth@w3.org>
>Of *course* it is! If you have an authoring tool that's integrated with your >browser (at least to the extent of being able to send it "go to this URI" >commands), that's going to make it a *lot* easier to test the content you've >developed. If the browser can't use the same URI as the authoring tool, then >you're going to have to do the translation by hand (which is essentially what >I have to do with Netscape Composer today, since my ISP doesn't support HTTP >PUT), or else teach the authoring tool to remap URIs that it sends to the >browser (possible, but messy). Give me a break, John. The Source URL is a link provided by WebDAV. If you are doing authoring on a resource, the user agent is already aware of both the retrieval interface (seeing the results) and the source interface (seeing the content from which the retrieval is derived). If they are the same thing, then it may be the same URL, or it may not. If they are not the same thing, then it won't be the same URL. Either way, the browser is going to be told to retrieve "a URL" by the Composer. This can all be done automatically by any sensible implementation of WebDAV once at least one of those two URLs are entered by the user to start the authoring process. The server will tell you the rest. ....Roy
Received on Monday, 21 September 1998 18:58:30 UTC