W3C home > Mailing lists > Public > www-rdf-interest@w3.org > March 2004

Re: HTTP Methods

From: Dirk-Willem van Gulik <dirkx@asemantics.com>
Date: Tue, 9 Mar 2004 11:31:36 +0100
Message-Id: <F11F21BD-71B4-11D8-B93F-000A95CDA38A@asemantics.com>
Cc: www-rdf-interest@w3.org, "ext Seaborne, Andy" <andy.seaborne@hp.com>
To: Patrick Stickler <patrick.stickler@nokia.com>


On Mar 9, 2004, at 11:21 AM, Patrick Stickler wrote:
> On Mar 09, 2004, at 12:05, ext Dirk-Willem van Gulik wrote:
>> On Mar 9, 2004, at 10:37 AM, Patrick Stickler wrote:
>>
>>> URIQA imposes *no* modifications to existing HTTP clients. All 
>>> enhancments are
>>>
>> I must be missing something fundamental. HOW does the client, who 
>> needs data
>> -about- the URL, i.e. the RDF, fetch that data ?
..
> If that client wanted a description of the resource denoted by the
> URI http://example.com/foo, it would submit a request
>
>    MGET /foo HTTP/1.1
>    Host: example.com
>
> Note that the only difference is the method used, and specifying
> the request method is part of the core HTTP client architecture.

Ok -- so the client MUST be modified in that case - i.e. on needs
to add code to do 'MGET' instead of 'GET' if the client wanted a
description of the resource denoted by the URL.

Dw
Received on Tuesday, 9 March 2004 05:31:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 18 February 2014 13:20:06 UTC