Eric Scheid wrote:
On 6/7/06 7:08 AM, "James M Snell" <[EMAIL PROTECTED]> wrote:
Whether or not to change atom:updated on an update request is
implementation specific and can only reasonably be determined by the
server. A server could choose to use the atom:updated value provided by
the client, but is not required to do so.
-1. "can only reasonably be determined by the server"??? Servers, generally
speaking, are not imbued with artificial intelligence. Determining whether
something is a "significant" update requires understanding who the audience
is, whether various laws have relevant jurisdiction, and understanding the
motives and agenda of the content producer.
I think the intent it to not require this in all instances. For
example, there are multiple ways into a collection in the database I'm
working on. If you come through the atom protocol door, the server
knows to update the collection entry's atom:update element. If you
come through some other door (e.g. WebDAV or custom server modules),
there is no knowledge of the feed entries.
So, is my server "broken" when someone updates that resource through
non-atom protocol means? I would say not.
--Alex Milowski
