The working group discussed this and decided to follow the HTTP standard (RFC 2616 [1]) for the behavior of the POST-response for Automation Requests. Section 9.5 states:
The action performed by the POST method might not result in a resource that can be identified by a URI. In this case, either 200 (OK) or 204 (No Content) is the appropriate response status, depending on whether or not the response includes an entity that describes the result. If a resource has been created on the origin server, the response SHOULD be 201 (Created) and contain an entity which describes the status of the request and refers to the new resource, and a Location header (see section 14.30). So, for your scenario I believe the appropriate response is a status code of 200 since the response includes the Request and Result entities. Comments? This might be an area where we need additional informative guidance in the specification. [1] - http://www.ietf.org/rfc/rfc2616.txt Regards, Mike Michael Fiedler IBM Rational Software [email protected] 919-254-4170 [email protected] wrote on 08/29/2012 05:42:48 PM: > Joe Ross/Austin/IBM@IBMUS > Sent by: [email protected] > > 08/29/2012 05:42 PM > > To > > [email protected], > > cc > > Denilson Nastacio/Raleigh/IBM@IBMUS > > Subject > > [Oslc-Automation] synchronous requests/results > > The spec mentions synchronous operations but doesn't really describe > how they work. For synchronous operations, our implementation > includes an AutomationResult in the response to the POST of a > synchronous AutomationRequest. We don't have anything in the > location header, since for this case, no resources exists in the > provider after the operation completes. Is there any problem with > that behavior? > > Thanks, > > ================================================ > Joe Ross/Austin/IBM, [email protected] > Tivoli Autonomic Computing & Component Technologies > 512-286-8311, T/L 363-8311_______________________________________________ > Oslc-Automation mailing list > [email protected] > http://open-services.net/mailman/listinfo/oslc-automation_open-services.net
