[Cosmo-dev] CMP POST /cmp/<username>/delete

[Travis Vachon]

This makes sense to me.

One thing to note, however, is that this is not identical to the  
other PUT/POST replacements, as the URL is also different (DELETE / 
cmp/user/<username> vs POST /cmp/user/<username>/delete).


On Jan 22, 2007, at 5:27 PM, Mikeal Rogers wrote:

> On Jan 22, 2007, at 5:20 PM, Travis Vachon wrote:
>
>> Hi folks
>>
>> Early in the 0.6 process we introduced POST /cmp/<username>/delete  
>> as a synonym for DELETE /cmp/<username> to get around the fact  
>> that some clients do not support the DELETE method.
>>
>> We have introduced an alternate solution to this problem, however,  
>> in the form of the X-HTTP-Method-Override header, making POST /cmp/ 
>> <username>/delete unnecessary.
>>
>> I'd like to propose that we remove POST /cmp/<username>/delete  
>> before 0.6 We are not using it anywhere, and since it is not part  
>> of an officially released version of CMP, I don't think  
>> deprecating it for a release is necessary.
>>
>> Any thoughts? If I don't hear differently, I'll commit this change  
>> tomorrow.
>
> The tests I just wrote verify that POST works for all CMP PUT  
> operations. I can change this easily but if we're doing this can we  
> please completely remove the POST synonymous with PUT functionality  
> from CMP.
>
> I think it's easier for us to say "this is the one way you can do  
> CMP operations with POST" rather than "all of these operations will  
> work with POST except delete which you must do this way". It also  
> makes my testing matrix ridiculous. At this point I don't think  
> that we have to worry about backwards compatibility with previous  
> CMP implementations, since ours is the only one.
>
> -Mikeal