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

Re: atom:updated not editable by the client?

To: Eric Scheid <eric.scheid@xxxxxxxxxxxxxxx>
Subject: Re: atom:updated not editable by the client?
From: Robert Sayre <mint@xxxxxxxxxxxxxxx>
Date: Wed, 13 Jul 2005 17:54:03 -0400
Cc: atom-protocol <atom-protocol@xxxxxxx>
In-reply-to: <>
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
User-agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317)

Eric Scheid wrote:

so, either the client needs to be able to edit and set the atom:updated
value directly, or it needs to be able to pass in a flag saying "this is
significant".

Or, the protocol can decide all protocol modifications are significant :)

Robert Sayre

Follow-Ups:
- Re: atom:updated not editable by the client?
  - From: Eric Scheid

References:
- Re: atom:updated not editable by the client?
  - From: Eric Scheid

Prev by Date: Re: PaceControlResource, PacePubControl, PacePubStatusResource... seeking consensus
Next by Date: Re: atom:updated not editable by the client?
Previous by thread: Re: atom:updated not editable by the client?
Next by thread: Re: atom:updated not editable by the client?
Index(es):
- Date
- Thread