[
Lists Home |
Date Index |
Thread Index
]
Hello Mark,
Mark said:
> Well, that's the whole point of this discussion. POST should not be
> used to "fetch results", because we already have a method that does
> that; GET. If you have more than one method that means "fetch stuff",
> then you've now got multiple independant information spaces, not a
> single one. WebDAV made this mistake with PROPFIND, as Dan Connolly
> described here;
>
> http://lists.w3.org/Archives/Public/www-tag/2002Feb/0091.html
>
Didier replies:
Good point. Thus, the whole issue though is to create a new URI that allows
us to encode the queries. If we use Karl Popper logic here, URLs showed
their limitations by being contradicted in several cases. If we say that
only the GET method can be used to fetch documents, then we have to create a
new URI. This is why millions of document fetching or dynamically created
documents are using the HTTP POST method. Simply because it is limited and
suffer from several usage breakdowns. Abstract URI concepts do not resolve
the issue. We have to propose a concrete one. Suggestions?
cheers
Didier PH Martin
|
