abdera-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James M Snell <jasn...@gmail.com>
Subject Re: POST vs PUT w/r to the response sent
Date Mon, 12 May 2008 16:10:58 GMT
The spec is silent on returning the entry with PUT.  It's left entirely 
up to the implementation.

- James

Remy Gendron wrote:
> Fair enough. Is this clear from the APP spec or is this left to the
> implementation to choose if the entry is returned on a PUT?
> 
>  
> Rémy
>  
> 
>  
> remy.gendron@arrova.ca
>  
> 418 809-8585
> http://arrova.ca
>  
> -----Original Message-----
> From: James M Snell [mailto:jasnell@gmail.com] 
> Sent: May 12, 2008 11:24
> To: abdera-user@incubator.apache.org
> Subject: Re: POST vs PUT w/r to the response sent
> 
> It's acceptable to return the entry in response to a PUT, it's just not 
> as critical as on the initial POST.  The assumption is that the user 
> already has the entry edit URI and the atom:id value so it can easily do 
> a GET if it wants the entry.
> 
> - James
> 
> Remy Gendron wrote:
>> Hello all,
>>
>>  
>>
>> On a POST, the entry is sent back in the response to return the a:id and 
>> an a:link(edit) and other information generated during the POST.
>>
>>  
>>
>> How come this is not the same for a PUT action? Business rules may 
>> change the content associated to an entry after a PUT. Shouldn’t the 
>> entry be sent back also? Or is this contrary to the HTTP PUT semantics?
>>
>>  
>>
>> Rémy
>>
>>  
>>
>>  
>>
>> Courriel:            remy.gendron@arrova.ca
> <mailto:remy.gendron@arrova.ca>
>> Cellulaire:          418 809-8585
>>
>> Site Web:          http://arrova.ca <http://arrova.ca/>
>>
>> Liste:                
>> http://mail.arrova.ca/mailman/listinfo/dev-list_arrova.ca
>>
>>  
>>
> 
> 

Mime
View raw message