Nate,
Why be specific with respect to just HTTP error status codes? What about
other client attributes like the HTTP header for "Content-Disposition",
etc.?
Nader
-----Original Message-----
From: Nathan Lipke [mailto:]
Sent: Wednesday, October 22, 2008 3:40 PM
To:
Subject: [wsrp-interop] No way to send HTTP status in response to a
getResource() call
Currently for getResource() (in-band resources) there is no way to
specify the HTTP status of the response. This is useful for a number of
use-cases including specifying 404 (Not found) and various REST style
use cases for 20x status codes. I would like to see a well-known
clientAttributes name(s) defined to carry the status code and message.
Any thoughts,
Nate
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
