W3C home > Mailing lists > Public > public-webapi@w3.org > August 2006

Re: XMLHttpRequest HTTP methods

From: Mark Baker <distobj@acm.org>
Date: Fri, 11 Aug 2006 16:38:38 -0400
Message-ID: <c70bc85d0608111338v18594d3pa13149130d1b1713@mail.gmail.com>
To: "Anne van Kesteren" <annevk@opera.com>
Cc: "Web APIs WG (public)" <public-webapi@w3.org>

SYNTAX_ERR sounds like a good start.  Not sure about SECURITY vs.
NOT_SUPPORTED though.

I've got a (partial) proposal for the bulk of the issue in my draft
folder, I'm just tied up with other stuff right now and have no time
to finish it up.

Mark.

On 8/11/06, Anne van Kesteren <annevk@opera.com> wrote:
>
> On Fri, 11 Aug 2006 14:15:23 +0200, Anne van Kesteren <annevk@opera.com>
> wrote:
> > I propose that for the open() method we throw a SYNTAX_ERR when the
> > first argument does not match the token production of RFC 2616 and a
> > (not yet defined) SECURITY_ERR when the method is not allowed for
> > security reasons. Depending on whether we go for a blacklist or
> > whitelist we can also have a NOT_SUPPORTED_ERR I suppose.
> >
> > For the user and password and perhaps the uri argument something similar
> > has to be done I guess.
>
> This is related to ISSUE-74 fwiw. If you want your thoughts to be recorded
> please mention the literal string 'ISSUE-74' in any follow-up e-mails.
>
>
> --
> Anne van Kesteren
> <http://annevankesteren.nl/>
> <http://www.opera.com/>
>
>
>
Received on Friday, 11 August 2006 20:38:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:55 GMT