On 2008-6-20 06:29, Paul Harrison wrote:
> Patrick Dowler write:
>> So the pattern would be to redirect to the job and always display >> the job.
For a programmatic client using XML that modifies a sub-resource, they already know the Location of the resource, so the redirect doesn't make much difference. I expect they would just POST (to the phase for example) and then ignore any 2xx or 3xx response and GET whatever they want to get next.
From the point of view of an XML-consuming client, the only place the redirect returns something informative is when you create the job (Location gives the URL to the job) and, if we added an input resource, when you create an input and get back the Location of the input.
From the pov of an HTML client, it actually drives the user experience.
Of course, this would apply to POST that modifies an existing resource. A POST that creates a new subresource should redirect to the created subresource.
-- Patrick Dowler Tel/Tél: (250) 363-6914 | fax/télécopieur: (250) 363-0045 Canadian Astronomy Data Centre | Centre canadien de donnees astronomiques National Research Council Canada | Conseil national de recherches Canada Government of Canada | Gouvernement du Canada 5071 West Saanich Road | 5071, chemin West Saanich Victoria, BC | Victoria (C.-B.)Received on 2008-06-23Z19:06:50