In: Categories » Internet » APIs and Web Feeds » Why Do You Need to Produce Feeds
|
Feeds have several advantages, primarily related to consumption, over traditional HTML formats. Many desktop applications are devoted to reading feeds at regular intervals, and many of the new batch of web browsers include features for reading feeds. These free the user from manually checking various sources (websites) for new information. Instead, the automated tool checks the subscribed feeds every few minutes and presents them to the user (usually organized in a user-configurable manner). The standard and predictable format makes this a much easier task than traditional page scraping methods that parse HTML. Feed aggregators are also coming to popularity on the Web with sites such as Planet PHP (www.planet-php.org/) and Feedster (www.feedster.com/). Finally, popular news sites (Google News, for example) compile the feeds of various news outlets to provide a single source of current news. By simply updating a corporate news/public relations page to provide a web feed, a company suddenly finds new outlets for its information, and by adding feeds to your own pages, you can make it easy and convenient for your audience to keep up to date with your content. Considerations When Producing a FeedOnce you discover how easy it is to produce a web feed and how easy the plethora of feed readers out there makes it for your users to consume your feed, you may have some inner drive to produce feeds for everything. Don't. First, as with any project, consider how useful the feed will be to outside users, what new information it will provide, and how it will be used. If this is a business site, consider how the feed will help achieve your corporate goals. Sure it would be cool to have a feed that ran the current weather in your office's city, but A) chances are you have windows (the look outside kind, not the operating system kind), B) a variety of sites already provide exactly this service, and C) is this something worth devoting resources toward? Second, consider the load requirements of generating the data. Remember that feeds are usually consumed by software automatically, at preset intervals. Many preset to small increments such as half an hour. Users who may have visited a given page once per day are now downloading the feed up to 48 times per day! Multiply that by the number of potential users, and you have a lot of additional traffic, and, unless you play your caching cards right, a lot of load on the server. Some of this, however, is negated by the smaller document size overall. For example, visiting http://slashdot.org/ involves a total of 23 HTTP requests, and a total size (images and all) of 21,819 bytes, whereas visiting http://slashdot.org/index.rss involves only one HTTP request, and only 4,515 bytes — definitely a significant savings. Finally, do consider the usefulness of this feed to your competitors. Placing all of your current pricing information or weekly production schedules in a feed may seem like a great boon internally (especially to upper management), but consider the repercussions if that URL becomes known to your competitors! Because feeds are generally consumed by software automatically, it can be more difficult to secure access. I strongly recommend against providing confidential data in a feed without first undergoing a strenuous security audit and seriously considering the alternatives. Publicizing Your FeedAs with any web project, your work is worthless unless you publicize it to your target audience. This is becoming easier and easier with some recent developments in the browser world. Mozilla in particular has made this quite easy in recent releases. When the browser sees the appropriate alternate link code in a document header, it presents an RSS icon in the lower-right corner of the browser window to inform the user, who may then create a "Live Bookmark" to monitor the feed. For example:
<LINK REL=" alternate" TITLE=" Slashdot RSS" HREF="//slashdot.org/index.rss"TYPE=" application/rss+xml">
However, publicizing your feed involves at least one more step. Create at least one page for your site that lists the URLs for the various feeds you will be providing, as well as what format the feeds will follow (RSS, Atom, and so on). You should also consider offering more detailed information about what type of content should be expected within the feed itself — what HTML tags should be expected, maximum length, and so on. This is important, because responsible, security-conscious users of your feed will need to filter the information they receive, and can make a much more intelligent decision about how to do that if you let them know what to expect.
|
legal disclaimer
1) Our website is not responsible for the information contained by this article as well for any and all copyright infringements by authors and writers. E-articles is a free information resource. If you suspect this article for any copyright infringements, please read the Terms of service and contact us to investigate the problem.
2) The E-articles directory team is not responsible for inaccuracies, falsehoods, or any other types of misinformation this tutorial may contain and will not be liable for any loss or damage suffered by a user through the user's reliance on the information gained here. Please read the Terms of service
Useful tools and features
If you like this article (tutorial), please link to it from your web page using the information above. Linking to this page, this is the only way to help us improve our service, the same time providing your visitors with a way to improve their online experience.
related articles
The two primary architectures for APIs are REST and SOAP. When creating your API, you really have three options: REST, SOAP, or both. REST APIs are known for being easy and quick to develop for, but the entire request is sent in the clear regardless of the type of encryption used. SOAP APIs are more complex, requiring more effort to generate the response and handle the request, but allow for greater flexibility by adding namespace support. Providing APIs of both types may sound like an attractive option, but keep in mind that it will double ...
2. Advantages and Disadvantages of SSL ~ API related
Configuring your web server to present the API over an SSL connection adds protection for both the request and response bodies, while requiring little to no additional coding for the API. Remember that the use of a server certificate only authenticates the server for the client, it does nothing to identify the client itself. It is best used layered with one of the previous two examples. Advantages: Encryption — Both request and response bodies are protected from intermediate prying eyes. ...
3. How SOAP Works
A SOAP request will involve creating and populating a request envelope, which contains all the required information (as specified by the WSDL document), transmitting that envelope to the API server, and handling the response. A SOAP request generally contains all of the following elements: SOAP Envelope — With namespace inclusions. SOAP Body — Possibly defining additional namespaces. Desired Action — How the desired action is represented will depen...
4. How REST Works
Generally speaking, a REST request will involve sending a request to a special URL (similar to what you would see after filling out a form using the GET method), then receiving an XML document containing the server's response. The XML response is then parsed, and the desired information is extracted and acted upon. Each REST request generally has several common elements: Endpoint URL — The full address for the desired script. A REST service might have only a single script that handles all request type...
There are two sides to this tale, the first is how to generate legitimate REST requests, and the second is how to handle the responses correctly. Generating Requests When it comes to generating the request, you have three main options. First, you can generate the request manually, using PHP's header functions. This gives you complete flexibility in generating the request, but does involve the most coding. Second, you can use one of PHP's built-in request functions such as file_get_contents() or file()/fopen(), fread(...
6. Important Considerations When Using Feeds
XML feeds provide a great resource of information, but their use is not without its own special considerations. Security and legal concerns go hand in hand whether you are producing or consuming feeds. Consider if you will the implications of going away for the weekend, only to discover that your aggregator has been attacked, your site is now displaying wildly inaccurate information provided by the attacker, and your legal department is fielding not-so-nice phone calls regarding the current content of your homepage. Also consider how often...
7. Advantages and Disadvantages of Client Side Certificates
The API server can generate a certificate and provide it to the client via a secure channel before any requests are made. This certificate is then used in the authentication process; this confirms the identity of both the client and server before requests are made. Although this method provides the greatest level of security (barring a dedicated VPN connection, which won't be covered here), it also has the most strenuous requirements on both sides: not all modules (say, NuSOAP) can handle client-side certificates. Advantages:...