[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: issue: Collection Document Fidelity

To: "Robert Sayre" <mint@xxxxxxxxxxxxxxx>, "Atom Protocol" <atom-protocol@xxxxxxx>
Subject: Re: issue: Collection Document Fidelity
From: "S. Mike Dierken" <mdierken@xxxxxxxxxxx>
Date: Wed, 16 Mar 2005 22:10:25 -0800
List-archive: <http://www.imc.org/atom-protocol/mail-archive/>
List-id: <atom-protocol.imc.org>
List-unsubscribe: <mailto:atom-protocol-request@imc.org?body=unsubscribe>
References: <>
Sender: owner-atom-protocol@xxxxxxxxxxxx

>
> "Hypermedia is the engine of application state", and it says I have ten
> posts, but really I only have nine because one is a 404.
A broken link might be due to the resource not having been created yet, or
might be due to having been removed in the past.
Distributed systems have latency and supporting 'broken links' allows for
parts to continue to operate while the system as whole eventually arrives at
'consensus'.

Just my opinion.

Follow-Ups:
- Re: issue: Collection Document Fidelity
  - From: Robert Sayre

References:
- issue: Collection Document Fidelity
  - From: Robert Sayre

Prev by Date: Re: issue: SOAP requirements
Next by Date: Re: issue: standard error messages
Previous by thread: issue: Collection Document Fidelity
Next by thread: Re: issue: Collection Document Fidelity
Index(es):
- Date
- Thread