Mailing-List: contact shindig-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: shindig-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of lryan@google.com designates
 216.239.45.13 as permitted sender)
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to:content-type;
	b=Ul7vejlVfcSLsbg74p7jKxJKvkGsyhD9JgxvMosM4BofTYIX5RrLlyZeBkg0D8QTj
	D+/7cXDPBHOKuOE95sgDg==
MIME-Version: 1.0
In-Reply-To: <c066cfd50811272225p3d8efe92s61c9283116fcf140@mail.gmail.com>
References: <2b27d1c80811170432n7f70f709gf8c68803ad414327@mail.gmail.com>
	 <818767740811190244h53da590j864a3b4cb8b76e11@mail.gmail.com>
	 <c066cfd50811272225p3d8efe92s61c9283116fcf140@mail.gmail.com>
Date: Mon, 1 Dec 2008 08:58:54 -0800
Message-ID: <7aa8716c0812010858y4b15058cvfe992045360ac6ab@mail.gmail.com>
Subject: Re: Shindig Error Codes
From: Louis Ryan <lryan@google.com>
To: shindig-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=001485e3b3b13da12f045cff208c

--001485e3b3b13da12f045cff208c
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

There was a somewhat drawn out discussion about this on the spec list and
409 was eventually agreed on despite its limitations. Until the spec changes
thats what it should be.

On Thu, Nov 27, 2008 at 10:25 PM, Ram Sharma <ramsharma2k5@gmail.com> wrote:

> Any updates on this ?
>
> On Wed, Nov 19, 2008 at 4:14 PM, Chris Chabot <chabotc@google.com> wrote:
>
> > 509 is an 'bandwidth exceeded' error, which sounds a bit like what it
> > represents, but not quite :)
> >
> > I'm ok with any of the options, but 409 sounds like a decent option to
> me.
> >
> > Anyone have any input on what they think it should be? And lets then make
> > the error codes the same between implementations :)
> >
> >  -- Chris
> >
> > On Mon, Nov 17, 2008 at 1:32 PM, Astha Bhatnagar <
> > asthabhatnagar2008@gmail.com> wrote:
> >
> > > Hi Shindig Dev,
> > >
> > > I have a question regarding to Shindig Error coodes.
> > >
> > > According to http://markmail.org/message/ahwnla6mnfkmswxr the Error
> code
> > > for
> > > Limit Exceeded should be 409 as it can be used for both conflict and
> > limit
> > > exceeded. But In JsonRPC container js file it is 417 written for
> checking
> > > the Limit exceeding error. In Restful container js file there is a
> place
> > > holder for the same. In PHP Shindig its 509 for the same.
> > >
> > > Accroding to opensocial-and-gadgets-spec discussion it should be 409.
> But
> > > by
> > > the definition 509 it seems to be more correct. However, 509 is not an
> > > official status code(see
> > > http://en.wikipedia.org/wiki/List_of_HTTP_status_codes).
> > > My question is what should be the correct code 509 or 409 or or
> > > 507(suggested in PHP comment) 417:P ? And shouldn't that code be
> > > homegenously used across all the implementations?
> > >
> > > any suggestions or comments ?
> > >
> > > should I post this on opensocial-and-gadgets-spec list too as a
> proposal
> > ?
> > >
> > > Astha
> > >
> >
>
>
>
> --
> Ram Sharma
>

--001485e3b3b13da12f045cff208c--