W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > January to March 2006

Re: HTTP Status Codes for QueryRequestRefused

From: Seaborne, Andy <andy.seaborne@hp.com>
Date: Wed, 11 Jan 2006 16:36:17 +0000
Message-ID: <43C53401.50609@hp.com>
To: Kendall Clark <kendall@monkeyfist.com>
CC: Steve Harris <S.W.Harris@ecs.soton.ac.uk>, RDF Data Access Working Group <public-rdf-dawg@w3.org>

Kendall Clark wrote:
> On Jan 11, 2006, at 5:28 AM, Steve Harris wrote:
>>I care, but I dont totally understand the issues (I'm WSDL  
>>illiterate). I
>>want to be able to send back any reasonable HTTP code for uncommon
>>conditions (eg. server segfaults, out of memory), but as far as I  
>>can see
>>you both think that should be OK.
> I do. I don't think Andy does because of the "must" and the broad way  
> he reads "refuses". But I've proposed text to Andy that he seems to  
> favor, so we'll see how that goes.
> My other suggestion was just to drop this WSDL fault completely. I've  
> convinced myself that it's pretty useless and unnecessary.

Axis uses faults in the WSDL description to generate code that throws the Java 
exception for the fault.


>>OTOH I could argue that at that stage its just not a SPARQL  
>>service, as
>>its not capable of processing anything at all.
> Exactly. The problem, of course, with overloading things is ambiguity.
> Cheers,
> Kendall
Received on Wednesday, 11 January 2006 16:36:37 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:00:50 UTC