[
Lists Home |
Date Index |
Thread Index
]
Is it a good 80/20 tradeoff though? IOW, how
often would an unchanged repeat occur and what
is the penalty?
I think that depends on the application of the
syndicated information. Again, the reliability
that Bob Wyman is discussing comes at a cost
of features and the trade offs vary by application.
If the scope of the application is drifting, there
is no single answer or best strategy, IME. What
David Megginson and John Cowan are discussing
with regards to NewsML apps looks right in that
context, particularly the reference to DRM. But
is it right for any and all applications of RSS/Atom?
And that brings us back to Joshua's point of
customer pull. Who is pulling and for what
application?
Techies can be customers. No D'oh, but scale
matters.
len
-----Original Message-----
From: Thomas B. Passin [mailto:tpassin@comcast.net]
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>
|
