edgar | 1 Oct 2005 13:32
Picon

Re (2): last calling WebDAV mounting spec


Hi,
after havin a look at the spec here my naive thoughts.
If I'm overlooking something just flame me :-)
As I understand it the idea is to tell a webbrowser that an URL it got is
WebDAV or even DeltaV capable.
But this is just meta information. Do why not something simple like:

GET /documents/user42/inbox HTTP/1.1
Host: www.example.com

Response:
HTTP/1.1 200 OK
Content-Type: what/ever; dav/deltav
Content-Length: xxx

The normal document for the browser ....
....

I hope you get the idea to give a hint in the header.
If what I'm proposing above would confuse a plain vanilla browser perhaps
there is another way.
This would tell the browser that it makes sense to open this URL with a
WebDAV client.
Because I think that much of the information in the dm: is redundant.

Chees, Edgar
--- start of oberon mail ---
:O <at> h=:<P3m]eE^Y]\b=V`dUCM\^eU6e]di3Bc0`7<0<P?88X0OZH;[LO[KSY<MiD7[K0Z060eM0H
67P8=]\\QQe\d]\b5TX=\f=]^5TQ5T\m]_M]P<\d5Td5]U5Tc5^UM\P4]UE^U5T]=_Pd]Q=]f]\P
(Continue reading)

Julian Reschke | 1 Oct 2005 14:07
Picon
Picon

Re: Re (2): last calling WebDAV mounting spec


edgar <at> edgarschwarz.de wrote:
> Hi,
> after havin a look at the spec here my naive thoughts.
> If I'm overlooking something just flame me :-)
> As I understand it the idea is to tell a webbrowser that an URL it got is
> WebDAV or even DeltaV capable.

Not just that. For instance, you may also want to initiate an "mount" 
request for a different URL. For instance, many document management 
systems use separate URL namespaces for HTML-based navigation, and 
HTTP/WebDAV access. Thus one level of indirection is needed anyway.

> But this is just meta information. Do why not something simple like:
> 
> GET /documents/user42/inbox HTTP/1.1
> Host: www.example.com
> 
> Response:
> HTTP/1.1 200 OK
> Content-Type: what/ever; dav/deltav
> Content-Length: xxx
> 
> The normal document for the browser ....
> ....
> 
> I hope you get the idea to give a hint in the header.
> If what I'm proposing above would confuse a plain vanilla browser perhaps
> there is another way.

(Continue reading)

Julian Reschke | 1 Oct 2005 21:40
Picon
Picon

REDIRECTREF issue "8.1_deep_lock_complexity", was: WGLC draft-ietf-webdav-redirectref-protocol-12


Geoffrey M Clemm wrote:
> 
> I agree with Julian that the Depth infinity section of redirectref should
> be redefined based on this implementation experience.
> 
> Cheers,
> Geoff

OK, I finally got around reviewing the issue. I have changed the spec 
based on the principle of "least client astonishment", letting the 
behaviour default to "the right thing". That is, non redirect-aware 
clients will see no difference when applying LOCK, COPY, MOVE or DELETE 
to a collection that may contain redirects. (Our server currently obeys 
the Apply-To-Redirect-Ref header for COPY and MOVE, but I'm not aware of 
any use case depending on that, so I'll simply change the behaviour).

Not surprisingly, the spec has gotten quiet a bit shorter because of that.

Feedback appreciated -- I'd like to submit this as a revised draft 
addressing all WGLC comments before the cutoff date for the upcoming IETF.

Best regards, Julian

--

Link to issue for tracking: 
<http://greenbytes.de/tech/webdav/draft-ietf-webdav-redirectref-protocol-issues.html#8.1_deep_lock_complexity>

Link to latest edits (includes change tracking): 
(Continue reading)

bugzilla | 3 Oct 2005 11:32
Favicon

[Bug 54] Locks vs multiple bindings


http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=54

julian.reschke <at> greenbytes.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|-06                         |-07

------- Additional Comments From julian.reschke <at> greenbytes.de  2005-10-03 02:32 -------
Secion 6.7 in draft 07
(<http://greenbytes.de/tech/webdav/draft-ietf-webdav-rfc2518bis-07.html#rfc.section.6.7>).

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

bugzilla | 3 Oct 2005 11:39
Favicon

[Bug 64] Incorrect IETF boilerplate


http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=64

julian.reschke <at> greenbytes.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

------- Additional Comments From julian.reschke <at> greenbytes.de  2005-10-03 02:39 -------
Fixed in 07.

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

bugzilla | 3 Oct 2005 11:44
Favicon

[Bug 55] Multistatus format (empty)


http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=55

julian.reschke <at> greenbytes.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|-06                         |-07

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

bugzilla | 3 Oct 2005 11:47
Favicon

[Bug 56] 423 Locked in Multistatus for PROPPATCH?


http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=56

julian.reschke <at> greenbytes.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|-06                         |-07

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

bugzilla | 3 Oct 2005 11:49
Favicon

[Bug 57] incorrect section reference


http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=57

julian.reschke <at> greenbytes.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|-06                         |-07

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

bugzilla | 3 Oct 2005 11:51
Favicon

[Bug 58] MOVE status 403 description


http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=58

julian.reschke <at> greenbytes.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|-06                         |-07

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

bugzilla | 3 Oct 2005 11:58
Favicon

[Bug 59] failed LOCK response body


http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=59

julian.reschke <at> greenbytes.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|-06                         |-07

------- Additional Comments From julian.reschke <at> greenbytes.de  2005-10-03 02:58 -------
Now in section 8.11.5
(<http://greenbytes.de/tech/webdav/draft-ietf-webdav-rfc2518bis-07.html#rfc.section.8.11.5>)

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


Gmane