http://wellformedweb.org/news/6 <p><a href="http://wellformedweb.org/story/2">Bulu</a>, the server-side code for RESTLog, is now available. This is a Python script released under the <a href="http://opensource.org/licenses/mit-license.php">MIT license</a> that I have tested under Apache on Windows and Linux. It implements the interface described in <a href="http://wellformedweb.org/news/5">The RESTLog Interface</a>. Note that it is not very useful without the client, which I will be publishing in a few days. I am making it available now as reference material for the descriptions of its operation.</p> <p> Before diving into the description of Bulu.cgi you may want to take a look at the <a href="http://hoohoo.ncsa.uiuc.edu/cgi/interface.html">CGI Specification</a> if you are unfarmiliar with how information is passed from the web server to a CGI application. By the description of the interface for RESTLog, particularly the table <a href="http://wellformedweb.org/news/5#RESTLogInterface">that summarizes it</a>, incoming requests need to be dispatched based on URL, Verb and Type. (Note that when I refer to Type I am talking about the abbreviated types in <a href="http://wellformedweb.org/news/5#TypeMappings">Type Mappings Table</a>.) The URL can be that of the CGI script alone or it can be the name of the CGI script with a path extension of the <i>itemID</i>. Inside a CGI script the path extension information is passed in via the PATH_INFO environment variable. Verb can be one of the standard HTTP verbs GET, PUT, POST and DELETE and this is passed in via the REQUEST_METHOD environment variable. Lastly the Type can be selected via <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec12.html#sec12">content negotiation</a> or set by a query string. That's a lot of information to consider when dispatching requests so in RESTLog it is broken down into two phases. For the first phase requests are segregated based on the URI they pertain to. Requests for the base URL <code>Bulu.cgi</code> are passed to the class RootDispatch to be handled. Requests for the item URL <code>Bulu.cgi/<i>itemID</i></code> are passed to the ItemDispatch class.</p> <p>Both RootDispatch and ItemDispatch derive from the same base class <code>BaseHttpDispatch</code> which has a single member function, <code>dispatch(self, verb, mime_type)</code> which dispatches requests based on the Verb and Type of the message. The dispatching is done by introspection (aka reflection for those familiar with .Net nomenclature) where the dispatch function looks for a member function of the class that has the name Verb_Type. If a match isn't found then it looks for the function with the name Verb. If none of those exist then an error code is returned. For example, if you POST an XML document to Bulu.cgi then RootDispatch will be instanced and when BaseHttpDispatch.dispatch is called it will first look for RootDispatch.POST_xml and if it fails to find that it will look for the member function RootDispatch.POST. In Bulu.cgi RootDispatch implements POST_xml and it is this function that is called when the client creates a new story by POSTing the item as XML to the URL <code>Bulu.cgi</code>. </p> <p>Tomorrow I will cover the simplistic templating mechanisms that RESTLog employs to format the content.</p> BitWorking, Inc http://wellformedweb.org/news/6#X1 <p>nama saya adalah hakimi saya bayak bulu<br /> saya anak ke 1000</p> 2004-03-01T21:26:24-05:00