We know what we want and we don't want to have to wait for it /end! It's embedded into our very fabric that whatever it is it needs to be delivered promptly!! Look around now and you will see people rapidly going about their business like their lives depend on it! The 21st Century is a 24 hour never sleeping buzz of activity, the Internet has made us dependant on the steady flow of information. We're always connected and the world seem like a much smaller place because of this and we want the information faster!
FriendFeed's Gary Burd and Paul Buchheit have a proposal to get the information faster through the pipes and they have named it Simple Update Protocol, or SUP. I have provided the details from the FriendFeed Blog below for you to digest ;-)
Benefits include:
- Simple to implement. Most sites can add support with only few lines of code if their database already stores timestamps. * Works over HTTP, so it's very easy to publish and consume.
- Cacheable. A SUP feed can be generated by a cron job and served from a static text file or from memcached.
- Compact. Updates can be about 21 bytes each. (8 bytes with gzip encoding)
- Does not expose usernames or secret feed urls (such as Google Reader Shared Items feeds)
Sites wishing to produce a SUP feed must do two things:
- Add a special tag to their SUP enabled Atom or RSS feeds. This tag includes the feed's SUP-ID and the URL of the appropriate SUP feed.
- Generate a SUP feed which lists the SUP-IDs of all recently updated feeds.
- Storing the SUP-IDs of the Atom/RSS feeds they consume.
- Watching for those SUP-IDs in their associated SUP feeds.