Lists Home |
Date Index |
> From: Mark Baker [mailto:firstname.lastname@example.org]
> Sent: Tuesday, April 23, 2002 8:51 PM
> To: Didier PH Martin
> Cc: Mark Baker; Francis Norton; Julian Reschke; Bill de hOra;
> Subject: Re: [xml-dev] What does SOAP really add?
> On Tue, Apr 23, 2002 at 02:22:07PM -0400, Didier PH Martin wrote:
> > Didier replies:
> > Good point. Thus, the whole issue though is to create a new URI
> that allows
> > us to encode the queries.
> More or less, yes. But I like to focus on "identifying resources"
> rather than "encoding queries". Think of a query as identifying
> something. For example, this query identifies all resources that
> Google knows about that includes your name.
> > If we say that
> > only the GET method can be used to fetch documents, then we
> have to create a
> > new URI.
> Yes!! This is a Good Thing.
> > 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?
> I think the creation of new URIs is a wonderful side effect (no pun
> intended 8-) of having a single "retrieve" method. Looking at
> PROPFIND again, if the "properties for a resource" were identified by a
> separate URI rather than retrieved via a non-GET method, then we could
> make assertions about the properties, cache them, use XSLT on them, etc.
> All the goodies you get by having a URI.
I agree, however this issue is really complex (just take a look at the
various PROPFIND parameters and headers). Actually, it would be nice if any
WebDAV property of a resource would have it's own URI. I'm certainly
interested in this problem (if only to enhance our own WebDAV server code),
so I invite everybody interested to start a discussion on the WebDAV mailing