Home > Archive > Microsoft Webservices > March 2005 > W3C Webservice Response Codes
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
W3C Webservice Response Codes
|
|
| Chris Fink 2005-03-08, 4:04 pm |
| Are there any standards in place, or any recommendations on how you do it
today, for standard response codes from webservices similar to the way an
HTTP response is sent across HTTP?
For example, suppose you offer several webservices from your company and
each service is handled internally in a different fashion. Some synchronous
that do their task and get the answer immediately, others that work
asynchronous and need to perform some additional work before the final
answer is provided. In these cases, I would like to provide a universal web
service status code indicating that the task is complete or pending. In
addition, if any errors arise due to internal errors, server timeouts, etc I
would like to return the appropriate status to the customer.
I understand that the return type of a webservice is defined by the
programmer and can be configured to return any custom defined status, but
what I am looking for is a universal way that are used by webservices; one
in which will involve less training to the person consuming our webservices.
| |
| Pete Wood 2005-03-10, 9:00 pm |
| I recommend you don't "hijack" the HTTP codes for indicating the status of
you're web service call. All web services should return HTTP SUCCESS
independent of which additional threads may be kicked off. I recommend you
define a customer STATUS element in the payload so the client knows if
another response is expected, or if thats the completed transaction. You
may also want to look at ws-transaction in WSE 2.0.
--
Peter Wood
Visit us at http://www.webserviceshelp.org/wsh
______________________________________
"Chris Fink" <chrisfink00@hotmail.com> wrote in message
news:OCqF9Y$IFHA.1200@TK2MSFTNGP10.phx.gbl...
> Are there any standards in place, or any recommendations on how you do it
> today, for standard response codes from webservices similar to the way an
> HTTP response is sent across HTTP?
>
> For example, suppose you offer several webservices from your company and
> each service is handled internally in a different fashion. Some
> synchronous that do their task and get the answer immediately, others that
> work asynchronous and need to perform some additional work before the
> final answer is provided. In these cases, I would like to provide a
> universal web service status code indicating that the task is complete or
> pending. In addition, if any errors arise due to internal errors, server
> timeouts, etc I would like to return the appropriate status to the
> customer.
>
> I understand that the return type of a webservice is defined by the
> programmer and can be configured to return any custom defined status, but
> what I am looking for is a universal way that are used by webservices; one
> in which will involve less training to the person consuming our
> webservices.
>
|
|
|
|
|