> Two of the current services supported by the application
> interface require input parameters (itemDetail and
> termUpdates). This is not a problem with SOAP since clients
> can be generated from the WSDL, and errors are thrown in an
> expected manner. However this is not the case with the REST
> style. These two services will have to expect invalid
> invocations, and respond in a manner that the applications
> invoking the services can interpret correctly. Correct
> invocations will retrun RDF/XML. I am guessing that invalid
> invocations should also, but don't know of a format that
> would be meaningful to an applicaiton. Any suggestions?
Maybe just return an empty model in RDF/XML with an HTTP status code of
4xx and an error message in the header? Not sure which code though....
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
Pete
|