Add guidance how to "migrate" from using POST to using QUERY

[dret]

Many people might consider using QUERY and they're currently using POST. It could be useful to provide some guidance what to take into account when planning such a transition.

[dret]

a procedural question: is it correct that this draft is authored in XML?

[mnot]

It is authored in XML, yes.

[reschke]

@dret - did you have something specific in mind? In general, we'll just change the method name. Things only get more complex when we want to leverage caching etc, no?

[dret]

mostly my thinking was to at least briefly describe the difference in HTTP semantics, with POST being unsafe and non-idempotent and QUERY being the other way around. this means that such a transition make sense for where POST had been used because GET doesn't support a body, but not necessarily in other cases. i know that @mnot isn't a big fan of writing guidance into specs, and i think that's usually a good approach. but because this one is specifically about moving from one practice to a different one, maybe some guidance could be helpful as an appendix, including at least mentioning SEARCH (RFC 5323).