* Jens Alfke <email@hidden> [2006-01-30 18:35]:
>Now, i think some of the confusion here stems from the fact
>that, for better or worse, the current protocol for subscribing
>to a news feed involves nothing more than repeatedly fetching
>it as a normal HTTP resource.
For better.
There’s a reason the web has scaled as it has, even though HTTP
appears so comically flawed that it could have been an April
fool’s joke in the IETF. It works *because* of its flaws, not
*in spite* of them.
Hence, the answer to the following:
>But that doesn't mean a feed should be treated as any other
>HTTP resource.
Yes it should.
>A feed is more than a static document like a JPG: its value
>comes from the fact that it changes over time in a meaningful
>way,
The same applies to streaming audio/video media. If you look at
how they’re handled, you’ll find that the browser downloads a
playlist with the appropriate MIME type and launches the matching
player, which then picks up the address from the playlist. It’s
robust and works.
There’s no reason feeds should work any differently, which is why
Atom is designed to work the same way.
Except that this is part of the laundry list of problems RSS
never addressed, and so for RSS, unlike for Atom, dealing with
the situation *requires* bogus crutches and you can’t win.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
syndication-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/syndication-dev/email@hidden
This email sent to email@hidden
