Hi,
see below some comments on the current draft.
Best regards, Julian
+++
1. Introduction
"First, the object is data transport agnostic - it supports any data
format, including XML."
Actually, it doesn't. As far as I can tell, it only supports text based
formats and XML. There's no way
On Sat, 17 Feb 2007 18:00:54 +0100, Julian Reschke <[EMAIL PROTECTED]>
wrote:
see below some comments on the current draft.
Thanks!
1. Introduction
"First, the object is data transport agnostic - it supports any data
format, including XML."
Actually, it doesn't. As far as I can tell,
Anne van Kesteren schrieb:
Actually, it doesn't. As far as I can tell, it only supports text
based formats and XML. There's no way to send or retrieve binary content.
Fair enough. In due course it will though. Fixed.
That would be great. It's a missing piece for writing a useful WebDAV
auth
On Sat, 17 Feb 2007 20:13:52 +0100, Julian Reschke <[EMAIL PROTECTED]>
wrote:
"Otherwise, if the nominated request header field already has a value,
the new value MUST be combined with the existing value (section 4.2,
[RFC2616])."
That's a bit misleading. What does "combine" mean precisel
On 2/13/07, Anne van Kesteren <[EMAIL PROTECTED]> wrote:
http://dev.w3.org/cvsweb/~checkout~/2006/webapi/XMLHttpRequest/Overview.html?content-type=text/html;%20charset=utf-8
as Last Call Working Draft by next Monday. If you have any objections
please post them to the public list.
Where do the
On Sat, 17 Feb 2007 21:15:04 +0100, Robert Sayre <[EMAIL PROTECTED]> wrote:
Where do the requirements for the username and password productions
come from? Is there an old list discussion on them?
Mainly offlist feedback. There's been some discussion (on list) on the
userinfo production thoug
On 2/17/07, Anne van Kesteren <[EMAIL PROTECTED]> wrote:
On Sat, 17 Feb 2007 21:15:04 +0100, Robert Sayre <[EMAIL PROTECTED]> wrote:
> Where do the requirements for the username and password productions
> come from? Is there an old list discussion on them?
Mainly offlist feedback. There's been
Anne van Kesteren schrieb:
That's a bit misleading. What does "combine" mean precisely? Is the
intent to require implementations to assume that the header format
is a comma-separated list?
Yes.
So please clarify.
Section 4.2 already talks about this quite explicitly. What do you want
it
Julian Reschke schrieb:
"User agents MUST at least support the following list of methods (see
[RFC2616]):
* GET
* POST
* HEAD
* PUT
* DELETE "
Why is OPTIONS missing from this list?
Because it's not generally supported and vendors had concerns about
it. If you can
