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

RE: Precepts of Goland

From: Jim Davis <jrd3@alum.mit.edu>
Date: Tue, 04 Jan 2000 23:28:35 +0100
Message-Id: <4.1.20000104232108.009fa820@pop.xs4all.nl>
Message-Id: <4.1.20000104232108.009fa820@pop.xs4all.nl>
To: w3c-dist-auth@w3.org
At 09:48 AM 1/4/00 -0800, Yaron Goland wrote:
>So Spoke Jim Davis:
>> Precept #1a - An HTTP client sends an HTTP request message  
>> to a server...
>What is the difference between throwing in a new object, called a server,
>and describing an instance of a resource called the null resource? 

Well, this is just my intuition speaking, but I think many people are
comfortable with the idea of a "web server" being some chunk of software
that listens on a port, accepts HTTP requests, and interprets them somehow.
 It's a relatively familiar notion.  Surely if I talk about "the Apache Web
server" or Microsoft's IIS, people know roughly what I mean.  I am less
sure that people have an intuition about a null resource, especially since
we seem to need both a "plain" null resource and a "locked null" resource.
but again, this is just a hunch.

Even if I am right, it could also be that that very familiarity makes it
treacherous -- because t might be carrying conceptual baggage that does not
belong, e.g. people might start expecting WebDAV to provide a live property
that contains recent log entries or something.

Rather than debate this point any further, I will be silent a while and see
if anyone else has anything more principled to offer than a bare intuition.
 Or perhaps there is yet another Initial Precept.


Received on Wednesday, 5 January 2000 02:04:16 UTC

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