Re: Guaranteeing the Integrity of Bindings

To give that dead horse one more kick (:-), I agree with John and Jason
that there is little useful we can say about the semantics of dynamic
resources.  The best we can do is give them some standard properties
like "source".

Cheers,
Geoff

   Date: Wed, 15 Sep 1999 15:27:47 -0400
   From: John Stracke <francis@ecal.com>
   X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i586)
   X-Accept-Language: en
   Mime-Version: 1.0
   References: <852567ED.006A4EC5.00@D51MTA07.pok.ibm.com>
   Content-Transfer-Encoding: 7bit
   Resent-From: w3c-dist-auth@w3.org
   X-Mailing-List: <w3c-dist-auth@w3.org> archive/latest/3317
   X-Loop: w3c-dist-auth@w3.org
   Sender: w3c-dist-auth-request@w3.org
   Resent-Sender: w3c-dist-auth-request@w3.org
   Precedence: list
   X-Lines: 27
   Content-Type: text/plain; charset="us-ascii"; conversions="7bit"
   Content-Length: 1145

   ccjason@us.ibm.com wrote:

   > > > We think that it is not impossible to guarantee integrity of bindings even
   > > > in cases like this, if the server is willing to take enough trouble.  It can
   > > > store a copy of the target resource locally, and insure that no changes are
   > > > allowed except when both servers are accessible.
   >
   > > It may not be feasible to make a copy of a dynamic resource.
   >
   > <opinion owner=jlc personal>
   > We've barely discussed dynamic resources in general.

   It doesn't take much discussion to realize that copying a dynamic resource is not
   something that can ever be expressed in a standard protocol; they're far too
   implementation-dependent.

Received on Wednesday, 15 September 1999 17:52:11 UTC