Posted on 02-23-2011
Superfeedr is now supporting PubSubHubbub for data APIs. PubSubHubbub was initially created for XML to alleviate the number of times a feed is polled versus how many times it actually has an update. The bandwidth consumption and server load of an API can be reduced greatly by adding a PubSubHubbub layer on a data API. Primary areas of a Superfeedr PubSubHubbub deployment are:
- Resource Identification - Identify what services your developers / applications are polling the most. Identify how many requests are made against how many times information was returned.
- Push Discovery - Indication to any applications polling your API that the content being polled is available in a push fashion by adding an HTTP header to the API responses which mentions the Superfeedr hub.
- Secure Subscriptions - Define a subscription callback URL where Superfeedr will echo all subscriptions to the API content, including the HTTP headers and any additional parameter provided by the subscriber.
Notifications - Superfeedr needs to know when content is updated so they can notify users. This is done in two ways:
- Fat pings - An API owner can push content to Superfeeder and they will parse the content and push it forward to subscribers.
- Light pings - Provide URL that has been updated and Superfeedr will update poll and update users.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- What Are Some Good Examples of Hypermedia APIs?
- API Driven Backend For Apps Using Orchestrate.io
- The APIs I Depend On To Run API Evangelist
- Service Composition for My Screen Capture API
- Liberate Government Data By Deploying Web APIs With Solr
- Moving Beyond My Basic 3Scale API Infrastructure Plan
- Next Steps For My Screen Capture API
- The Levers, Dials, And Switches For Your Participation In The API Economy
- Help Improve This Content: Another Reason To Deploy API Developer Area on Github
- Exploring What Is Next For The Green Button API