RE: API Rate Limits and HTTP Code [#255]

We send this mail from a law firm.
We are not interested in receiving emails advertising.
Under Law 34/2002 of 11 July, Services of information society and electronic commerce, you are notified about the responsibility that you may incur if you keep sending emails.
We want that our data are deleted from its database
Sincerely.

EVIAL ASESORES
Juan M. Sierra Lebrón
jsierra@economistes.com 
C/ Pau Claris, 190 - 2º 1ª  -  08037 Barcelona
Telf. 935 157 234 -  Fax 934 873 677

Cláusula confidencial
El contenido de este mensaje y cualquier documento adjunto al mismo son confidenciales. Tienen el sólo propósito de su uso por el individuo o entidad designado como receptor. Si recibe este mensaje por error, se le informa, que su lectura, divulgación, copia o distribución está estrictamente prohibida y le rogamos nos lo notifique por e-mail a (jsierra@economistes.com).
 Antes de imprimir este e-mail, piense bien si es necesario hacerlo.


-----Mensaje original-----
De: ietf-http-wg-request@w3.org [mailto:ietf-http-wg-request@w3.org] En nombre de Eric J. Bowman
Enviado el: viernes, 29 de octubre de 2010 3:45
Para: Mark Nottingham
CC: Karl Dubost; HTTP Working Group
Asunto: Re: API Rate Limits and HTTP Code [#255]

Mark Nottingham wrote:
> 
> a) Clarify that 503 can be used for rate limiting, or
> 

+1

I just came across this issue, too, but didn't bookmark -- Twitter's
Fail Whale is a 503; now cute rate-limit responses are proliferating,
but not everybody agrees on what status code to use, which surprises me.
I always assumed rate-limiting was kinda the whole point of 503.

-Eric

Received on Friday, 29 October 2010 07:54:08 UTC