[OSM-dev] DELETE + body not commonly implemented

Noel Grandin noel at peralex.com
Thu May 15 08:38:21 BST 2008

I would think that library support would be less of an issue than proxy

I know that subversion has ongoing hassles because they use an "unusual"
Every time my company changes ISP I have to log a request to get them to
fix their proxy.

Anyone know what the status is of "DELETE" support in internet proxies?

bvh wrote:
> On Wed, May 14, 2008 at 09:20:57PM -0400, Christopher Schmidt wrote:
>> One of the bigger changes in the 0.6 API from an implementation
>> perspective for clients may well be the use of a content body on DELETE
>> requests. kleptog found that to be the most difficult part of
>> implementing the changeset/versioning support for JOSM, I think, and I
>> think that a number of libraries may make this more difficult than one
>> would first assume, since DELETE+body is rather unusual.
>> There are two different ways to implement an alternative without
>> requiring changes to other code, neither of which would be particularly
>> difficult to implement, I don't think: 
>>  * Use ?query=string&args=forinfo
>>  * Use Version:/Changeset: headers.
> * Use DELETE /api/0.6/way/#id/#version
>> Either of these will probably work in a wider variety of HTTP clients,
>> some of which explicitly don't support including data in a DELETE
>> 'natively'.
> And if they support it, it is likely a less well tested future with
> bigger possibility of bugs.
>> What HTTP libraries are people using to talk to OSM? Do they easily
>> support DELETE with content body?
> Qt support this.
> cu bart
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev

Disclaimer: http://www.peralex.com/disclaimer.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20080515/437e3890/attachment.html>

More information about the dev mailing list