I suck ... On 28 Jun 2011, at 10:38, Mischa Tuffield wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello, > > On 28 Jun 2011, at 07:46, Michael Hausenblas wrote: > >> >>> Should we be returning 500 instead? >> >> Yes. To be more concise, I'd think that 503 [1] is appropriate. A 4xx is not >> appropriate IMHO, because [2]: >> >> [[ >> The 4xx class of status code is intended for cases in which the client seems >> to have erred. >> ]] > > Indeed 503 seems like the right thing™ to use, Yahoo's response codes may be > a good place to look at an implementation of a webservice. And here is the link to the BOSS documentation : http://developer.yahoo.com/search/boss/boss_api_guide/BOSSv2_FAQ.html Mischa > > Mischa > >> Cheers, >> Michael >> >> [1] http://tools.ietf.org/html/rfc2616#section-10.5.4 >> [2] http://tools.ietf.org/html/rfc2616#section-10.4 >> -- >> Dr. Michael Hausenblas, Research Fellow >> LiDRC - Linked Data Research Centre >> DERI - Digital Enterprise Research Institute >> NUIG - National University of Ireland, Galway >> Ireland, Europe >> Tel. +353 91 495730 >> http://linkeddata.deri.ie/ >> http://sw-app.org/about.html >> >> On 28 Jun 2011, at 07:21, Bill Roberts wrote: >> >>> Looking for some advice from the community. If we time out a slow-running >>> SPARQL query, what is the most appropriate HTTP status code to return to >>> the client? We had been trying 408, but the problem with that is that some >>> clients (notably Firefox) take it on themselves to keep retrying the >>> request, which isn't really what we want. >>> >>> Should we be returning 500 instead? >>> >>> Thanks >>> >>> Bill >>> >>> >> >> > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.12 (Darwin) > > iQIcBAEBAgAGBQJOCaEcAAoJEJ7QsE5R8vfvFwMP/0sC4MItGAXaGEfr6FvDuauo > WcvPTmZPVkaZQqjCaHGrk5h1nLotuV0/yirAN5wEaibUdKDBbQbmOqSqjvspvIGS > YXuH6wvB7jze4odwxl5M7Vae6/9MBODYeRiHGh46LZreSzGw0km50SQltozNZ93D > O6VAIq/bfOpGdYB4FpRqNhhNr120pd6HRx+zzUTL/naLkYek/BI6Tj23jwrBiiSd > DxQNOEeAA4VzvAhWU5hBloDtU3b5aSMgXr0k3Spkorj0/3ayZg2Zk+P00POMHHiz > W1fh5puV16SNSPQZtA9yD4gJxjrjSJoKgzdNq2MPcveurYrCosm4mRrLcBy4AV76 > FLVOy7NLax274Poptsvix9uRcdYnTnhpfTZv0sdT8hTNQmhJtvdBO4PLtUPIvyOA > 7XP1Oe6JleZ+I8e4KOakuzLjosmeeiNY/ZdOVSWyzRzKowlrG5ftn5hNMt7csDp+ > mHt87587vqMuIzyc7TfEdUUM1d3hwQI1uI2oBgWzNZ1PjpEyjLxgFq1UXtLwM0PC > 1PVNA8dRjqwmywdMzsIF0DE2EiSCUjNcnNxMBHH7W7+dLPDzSq6+egcwuO9KMqP8 > nZMnB5vaTGFydvuMb5jaWkuTUCjuuSRFr/du1gSmiEmRjnMKe70uyhJ0SWljVz67 > mP3Lft5SnUQPmcK+GKXS > =vPwh > -----END PGP SIGNATURE----- >
PGP.sig
Description: This is a digitally signed message part
