W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 1998

RE: Optional Backpointers from Targets to References

From: Lisa Lippert (Dusseault) (Exchange) <lisadu@exchange.microsoft.com>
Date: Wed, 16 Sep 1998 09:52:22 -0700
Message-ID: <2FBF98FC7852CF11912A000000000001090F5AEC@DINO>
To: "'Jim Amsden'" <jamsden@us.ibm.com>, w3c-dist-auth@w3.org
A couple possible solutions to the issue you present Jim...

1.  Such granular properties can be tractable if good inheritance is defined
and used.  Most properties may have the same ACLs as the resource they are
on.  Most resources may have more or less the same ACLs as their parent
collections.  This cuts down a great deal on storage, at least.

2.  Properties that are "read-only" need not be marked as such by ACLs.
"read-only" means that nobody can write to the property, therefore no write
ACLs are necessary.  If the system calculates the property and changes it
that's fine -- that's not covered by ACLs.  So John invoking ACLs may have
been just a short form for "the server can control write access to the
property on all resources" not necessarily "create an access control entry
on the property on this resource".  I'm putting words into your mouth John,
so correct me if I'm wrong.

Lisa

-----Original Message-----
From: Jim Amsden [mailto:jamsden@us.ibm.com]
Sent: Tuesday, September 15, 1998 4:21 PM
To: w3c-dist-auth@w3.org
Subject: Re: Optional Backpointers from Targets to References


This will require ACLs on individual properties, something many servers may
not
do as it presents a significant administration burden compared to simple
CRUD
ACLs. ACLs for every user, on every resource, for each resource property,
for
every WebDAV method is not tractable. We are rapidly reaching a scaleability
problem.





w3c-dist-auth-request@w3.org on 09/15/98 05:51:01 PM
Please respond to w3c-dist-auth-request@w3.org
To: w3c-dist-auth@w3.org
cc:
Subject: Re: Optional Backpointers from Targets to References

Jim Amsden wrote:

> And third, creating a
> reference to a resource will require modification of the target resource
to
> update its properties

I don't believe that has to be a problem.  The ACLs can be set up so that
they
specifically permit the backpointer property to be updated by the server.
(Come
to that, it's a live property, so write access may not mean very much in the
first place.)

--
/====================================================================\
|John (Francis) Stracke    |My opinions are my own.|S/MIME supported |
|Software Retrophrenologist|=========================================|
|Netscape Comm. Corp.      |"But she calls her ship _Mercy of the    |
|francis@netscape.com      | Goddess_!" "Kali." "Oh."                |
\====================================================================/
New area code for work number: 650
Received on Wednesday, 16 September 1998 12:52:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:47 GMT