This is almost identical to the way this (Web server type)
This is almost identical to the way this entry would appear in a feed. Rather than identifying the particular procedures within an application to which the individual data values should be passed, the RESTful approach is to pass the relevant data to the server using an HTTP method applied to specific URI. To create a new blog entry the message above could be passed to a server-side blogging tool s edit URI using the HTTP POST method. Server Consumer The job of a Server Consumer in this categorization depends a lot on the kind of setup. A straightforward Web-based blogging system is likely to use a simple form to pass data from the author to the server software for creating a new post or editing an existing one. In such a scenario, there isn t really a clean separation between Client Producer and Server Consumer. However, the tool that creates the content and the server-side system that consumes it can be separate. From an RSS point of view, a typical kind of Server Consumer would be the piece of software that receives blog post data (probably over XML-RPC) and passes it back to backend storage /or to the components of the system, which then look after generation of the blog pages. As it happens, many of the popular Web-based blogging systems support creation and editing of posts both by direct HTML form interfaces as well as calls from remote XML-RPC clients. As well as the usual author-driven route to content creation, material can come from other sources. Strictly speaking these should perhaps be listed here as either Client or Server Producer, but as producers they aren t really systems in their own right. More to the point, it s the developer of the Server Consumer that deals with data from these sources. Weblog Comments Most content-management tools such as blogging systems support reader comments. In principle, the system requirements for this facility are identical to those needed for handling material from the original author. In practice, things can get more complicated when dealing with material submitted by third parties. An authentication system might be necessary, and if anonymous posters are allowed, there is a likelihood of receiving comments from automated systems designed for the purpose, such as comment spam. Trackback This technique is one of the more interesting innovations to come from the Weblogging world. Using trackback, if you refer to a post on someone else s blog on your own blog, and then a reference to your remarks can appear on that other person s blog. There is a standard way of implementing trackback based on the original specification, which was designed for the Movable Type blog authoring tool. Systems that support trackback assign every published item a particular URI to which a trackback ping can be posted. Data posted to that URI in the correct format shows up alongside the comments made locally about the item. The complication is that when you include a link in your blog post, your system has the URI of the entry itself, not the remote entry s trackback URI. However, systems that support trackback usually include a block of hidden markup as part of the entry, which contains machine-readable details of the entry, including its trackback URI. So when you link to someone s post, your blogging system visits that link, retrieves the trackback URI, and then posts an extract of your remarks to the other person s blog. We discuss trackback, and several other inter-system protocols, in greater depth in Chapter 31. 233 Systematic Overview
Searching for affordable and reliable webhost to host and run your web applications? Go to our java web server services and you will be pleased.