The Verbosity of Echo
Sam Ruby has called for people to start experimenting with the current (very early) Echo example feeds, and the response has been pretty impressive; check out these feeds from Joel Spolsky, Phil Ringnalda and Mark Pilgrim. Now that Echo has progressed to a stage where there are concrete feeds to examine, I have some serious concerns over the verbosity of the format. As they stand, Echo feeds contain a lot of duplicated information. Considering that the default behaviour of aggregators is to poll a feed for updates once an hour, any unnecessary information in the feed itself is going to have a very real monetary cost in terms of burnt bandwidth.
I’ve posted some further thoughts on this subject in Sam Ruby’s comments, but I think the Echo development community need to spare some thought for the size of the feed. I’ve seen the justification before that requiring elements rather than making them optional makes it easier to write Echo implementations and I agree that this is a worthwhile consideration, but I think the trade-off in terms of additional bandwidth costs needs to be given a higher priority.
To that end I’ve proposed a small alteration to Echo to remove redundant author information from entries. If you are following the development of Echo I encourage you to take a look.
On a related note, this Java blogger has some interesting thoughts on the WikiNature (or lack there-of) of the Echo Wiki.
What about using RSS 3.0 instead then ;-)
http://intertwingly.net/blog/index.txt is very nice and concise, doesn't waste any bandwidth...
To be honest, I don't see why the format needs to be XML based instead of something like that. It's not as if the XML structured markup conveys more meaning. So why are we only considering an XML based format?
Peter - 2nd July 2003 18:57 - #
Simon Willison - 2nd July 2003 19:28 - #
Copied from Sam Ruby's comments: “What percentage of clients use conditional GET requests?”
Arien - 3rd July 2003 18:31 - #