[
Lists Home |
Date Index |
Thread Index
]
- To: "Thomas B. Passin" <tpassin@comcast.net>,"XML DEV" <xml-dev@lists.xml.org>
- Subject: RE: [xml-dev] best practice for providing newsfeeds ?
- From: "Dare Obasanjo" <dareo@microsoft.com>
- Date: Tue, 3 Feb 2004 15:19:05 -0800
- Thread-index: AcPqpIZBiwCnQdZ1TuOAUThu1YpQlwAB2JoQ
- Thread-topic: [xml-dev] best practice for providing newsfeeds ?
That doesn't work, because an item can remain in the feed between
requests and not be updated. What does work is hashing the content based
on the ID and if the content hash for an ID changes then you know it's
changed. Based on the conversation I just had with Joshua in his office
this is what he meant.
-----Original Message-----
From: Thomas B. Passin [mailto:tpassin@comcast.net]
Sent: Tuesday, February 03, 2004 2:26 PM
To: XML DEV
Subject: Re: [xml-dev] best practice for providing newsfeeds ?
Dare Obasanjo wrote:
> They are orthogonal problems. The problem isn't how to avoid repeating
> an item, it is how to show one has been changed since the last time
> the reader saw it.
>
I think the idea is that if you see an item and you already have seen
its GUID before, then you know it has been changed. That will work in a
single client but it will mislead you if the feed repeats an unchanged
item for whatever reason.
Cheers,
Tom P
-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>
|