W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2000

Re: Translation in the Tower of Babble

From: Geoffrey M. Clemm <geoffrey.clemm@rational.com>
Date: Wed, 5 Jan 2000 23:53:48 -0500
Message-Id: <10001060453.AA18659@tantalum>
To: w3c-dist-auth@w3.org
   From: Yaron Goland <yarong@Exchange.Microsoft.com>

   Corollary #1.3 - Since HTTP request messages can only be handled by
   resources which respond with HTTP response messages then 
   even error messages
   such as "Not Found" must have been generated by a resource.

   Well if the resource can't handle HTTP request, the daemon 
   that will ask
   this resource to generate an HTTP reply should return to the client an
   error stating that the resource doesn't support this 
   protocol, like a Not
   Found with a good explanation in the body.

   Perhaps I'm misunderstanding but I assume you are just confirming that you
   agree with #1.3. The resource which sent the "HTTP not supported" response
   is an HTTP resource. What the resource is saying is "I don't want to talk to
   you in HTTP." However the only way he could say that is if he supported
   HTTP. He is still an HTTP compliant resource and therefore it was a resource
   (in the object model) that generated the response.

For me, saying that "every resource must be an HTTP resource so that
it at least can say that it doesn't understand HTTP requests" is
another result of trying to eliminate the concept of a "server" (what
Yves calls a "daemon") from the model.  I believe a simpler (and more
intuitive) model is to just say that there is a server, and if the
server sees that a resource at a URL is not an HTTP resource, it
returns an "HTTP not supported" response.  This is the same server
object that owns the NR (name-to-resource) mapping data.

Received on Wednesday, 5 January 2000 23:53:54 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:21 UTC