OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-interop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [wsrp-interop] No way to send HTTP status in response to a getResource() call


I think the problem is what's in clientAttributes?  It's very loosely
defined in the spec as to what it will contain and you're essentially making
it more specific.  I'm OK with more specificity like:

"If it is not these two well known names related to the HTTP status code
info, then it is an HTTP header name ..."

Or some other similar statement that tells you what it contains.  The
problem could be in potential name clashes should something new come along.
At that point, you may wind up with WSRP specific names that map to
different HTTP names/codes/operations/etc.  

I think the options are:

1) Define all the names in WSRP and the mapping back to HTTP Or

2) Specify a rule similar to the above

What form this takes (recommendation, notes, etc.) is another matter.

Nader

-----Original Message-----
From: nathan.lipke@oracle.com [mailto:nathan.lipke@oracle.com] 
Sent: Monday, October 27, 2008 11:23 AM
To: wsrp-interop@lists.oasis-open.org; Nader Oteifa
Subject: RE: [wsrp-interop] No way to send HTTP status in response to a
getResource() call

You can already set headers using the client-attributes.

Nate

--- Original Message ---
> 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:nathan.lipke@oracle.com] 
> Sent: Wednesday, October 22, 2008 3:40 PM
> To: wsrp-interop@lists.oasis-open.org
> 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
> 
> 
> 
> 
> ---------------------------------------------------------------------
> 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
> 
> 




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]