barcode fonts for excel free download Under the hood in Java

Create Quick Response Code in Java Under the hood

Table 3.1 Well-known blog and wiki servers for a variety of platforms Type .Text Blojsom Bloxsom Confluence Das Blog Drupal Greymatter JSPWiki Moin Moin Movable Type Pebble PyBloxsom Roller Blog Blog Blog Wiki Blog Blog Blog Wiki Wiki Blog Blog Blog Blog Platform Windows Any/Java Any/Apache Any/Java Windows Any/Apache Any/Apache Any/Java Any/Apache Any/Apache Any/Java Any/Apache Any/Java Bundled app server Any/Apache Any/Apache Any/Java Any/Apache Any/Apache Language C# Java Perl Java C# Perl PHP Java Python Perl Java Python Java Storage RDBMS Files Files RDBMS Files RDBMS Files VCS or files VCS or files RDBMS or files Files Files RDBMS License Open source (BSD) Open source (BSD) Open source (MIT) Commercial Open source (BSD) Open source (GPL) Open source Open source (LGPL) Open source (GPL) Commercial Open source (BSD) Open source (MIT) Open source (Apache ) Open source (GPL) Commercial Open source (LGPL) Commercial Open source (GPL) Open source (GPL)

Different types of storage are abbreviated as follows:

Summary

That brings us to the end of our exploration of blog and wiki server technologies. Let s summarize what we have learned.

3.4 Summary

There s a wide variety of blog servers, but they all share similar feature sets, data models, and architectures. The same applies to wiki servers. Not all blog servers support group blogs, publishing workflows, hierarchical categories, or user-customizable templates; so if you need those features, shop carefully. Most wiki servers support limited blogging capabilities but don t offer all the features and flexibility that blog servers offer. For single-blog sites, consider using an easy-to-install file-system based blog server such as Pebble or Blojsom. For large multi-user blog sites, consider using a database-backed blog server with good support for caching, clustering and user-management features such as Roller. If you have a preferred operating system platform or programming language, choose a blog or wiki system that works well there.

A little history lesson on newsfeed formats will help you understand the choices you have and the direction that newsfeed technology is headed.

One of the first challenges developers face when building applications with RSS and Atom is making sense of the many slightly different XML newsfeed formats. The most popular newsfeed format is RSS, but RSS is not really a single format. RSS is a family of informally developed and competing formats that has forked into two opposing camps, which can t even agree on what the letters RSS stand for. In this chapter, we ll help you through this confusion by explaining the history of RSS, the RSS fork, and the details of the most widely used RSS formats. We ll also explain that, at least in the world of newsfeed formats, there is hope for the future. The Internet Engineering Task Force (IETF) has developed a new newsfeed format, known as the Atom Publishing Format, or Atom for short, which will eventually replace the RSS family of formats. We ll cover the details of the Atom format in this chapter and look at its sister specification, the Atom Publishing Protocol, in chapter 10. But for now, let s get started with our RSS history lesson.

RSS began life at Netscape as part of the My Netscape project. It was given the name RDF Site Summary (RSS) because it was an application of the Resource Description Framework (RDF), a sophisticated language for describing resources on the Web. Netscape used RSS to describe news stories and to allow users to build their own information portal, called My Netscape, by selecting the news sources they wanted to have displayed in their personal portal. RSS caught on quickly, as web sites scrambled to provide newsfeeds compatible with Netscape s innovative new portal. By the time Netscape developer Dan Libby produced the first specification, RSS 0.9, in January 1999, the RSS user community was already starting to divide into two camps. One camp wanted Netscape to make better use of RDF in RSS, and the other wanted to simplify RSS by removing RDF altogether. Influential blogger Dave Winer of Userland Software was among those arguing for simplicity and the removal of RDF. In the end, Winer s camp won.