Web design templates - Architectural Approaches The chapters that follow pick up
Architectural Approaches The chapters that follow pick up on various aspects of RSS and Atom programming mentioned in the earlier sections of the book and those outlined in this chapter. Before moving on, be aware that there is a wide spectrum of approaches to development. Approaches range from the use of formal methodologies that demand significant up-front design, to more agile approaches that focus on continuous integration of new code into existing systems. This spectrum is reflected not only in the applications produced, but also to some extent in the design of Web formats and protocols. The Web is remarkably flexible in the way it can successfully support anything from the most rigid formal design to the most ill thought out five-minute hack. Most syndication development falls within these two extremes. In practice it s possible to apply virtually any developmental approach to any aspect of RSS and Atom programming. What you will see is plenty of architecture by implication, where the code comes before the design, although a lot of the time any successes are due in part to the implied architecture corresponding directly with existing solid architecture. Without some sense of an architecture, there can be hidden risks. On the other hand, you aren t likely to see much of the architecture astronautics found in some Web services development, nor are you likely to see many back-of-envelope doodles being adopted as specifications (at least until they ve had some testing in the field). Because it builds more on existing languages you will tend to see more big picture architecture around RSS 1.0 and related specifications, and more throw it against the wall and see what sticks around RSS 2.0. Atom has steered a course somewhere in between. Whatever your own personal preferences, you should at least familiarize yourself with the best-practice recommendations in Architecture of the World Wide Web (www.w3.org/TR/webarch/). Summary In this chapter you learned… . How most parts of syndication systems fall into one of four categories. . The general nature of subsystems in each of those categories. . The significance of state, resources, and representations on the Web. . The basics of HTTP client-server communication. . How syndication systems use a polling protocol. In the chapters that follow you will see a lot more of the internals of the different parts of syndication systems, beginning with a high-level view of the data modeling needed for working with all kinds of feed data. Exercise 1. The first example of HTTP server code in this chapter was InflexibleServer.py, which served up the same string whatever page was requested. You also saw ZippyClient.py, an HTTP client that knew how to manage data from a server that supported compression. Your task is to create a modified version of InflexibleServer.py to gzip its data before serving it, so ZippyClient.py can talk to it. To get you started, here is a method that will take a string and gzip it: 234 Chapter 19
If you are looking for affordable and reliable webhost to host and run your business application visit our ftp web hosting services.