Designing a protocol to meet the limitations of existing deployments is
the wrong approach. Yes, we need to take those limitations into
account, but if existing deployments need to evolve, then so be it.
I've implemented APP on WordPress in my own test environment. If the
only limitation is that some hosting providers may not support PUT and
DELETE, that is their own problem to resolve, not ours. Let those for
which this is a problem define the solution as an extension.
- James
Tim Bray wrote:
On Feb 12, 2006, at 1:03 PM, David Powell wrote:
I was talking to Matt Mullenweg yesterday and he remarked that he
didn't think WordPress could realistically support APP as it stands
now, because WP is commonly used by people on low-rent hosting
providers and quite a few of those don't support the use of PUT and
DELETE.
Is this really the case? Doesn't Apache forward PUT and DELETE
requests through to CGI scripts, just like it does for GET and POST.
Absolutely. The problem isn't Apache. The problem is that certain
hosting providers refuse to allow PUT and DELETE on their hosted
servers. -Tim
