View: Blog Submissions: page 2 of 2
1 2 Restlet Cookbook - Form Submission and Processing (Recipe 3)
After describing some basic approaches and coding while designing and implementing a Web site using Restlet framework, let's consider next step - showing and submitting a Web form. Using Restlets, it's as easy as just showing simple Web pages. 10/15/2007 by Serge Ilyn
Restlet Cookbook - Site Application (Recipe 2)
Perhaps I should have started my "Restlet cookbook" series with this recipe since it describes the way you may code your main application class. Its main() method is called when you start your Web application. The reason I did not do this is that the first Recipe deals with two most important cornerstones of the Restlet framework - Resource and Representation classes. Recipe 2 shows the plumbing of various framework concepts to create a real life Web site. 10/04/2007 by Serge Ilyn
Restlet Cookbook - An Approach To Site Design (Recipe 1)
The beauty of the Restlet framework is in its conduciveness to the object-oriented design. When you design and implement a Web application in Restlet, you do not think about "J2EE" patterns - you think about and use classic software design patterns. The main benefit is that you can focus more on user requirements instead of intricacies of a particular J2EE Web development framework. As usually with OOA/OOD process, you go through a number of iterations while your understanding of the problem domain is growing. At the same time, you can exercise very good control over the costs of your project; the result of your effort is a design tailored not only to user requirements but also to how much effort you want to invest in it. This recipe shows an approach to the design of a "visual" Web application using Restlets. 09/27/2007 by Serge Ilyn
Restlet Framework - A Rising Star?
It looks like. Naviquan.com is running now on Restlet framework. This project started when I decided to get rid of "dynamic" URLs (the one that have question marks following by request parameters - something like …?id=xyz&month=mm&year=yyyy) and replace them with what some people call RESTful URLs (or "user friendly" URLs).
Naviquan.com is still in its beta phase with multiple problems to solve (most of them are non-technical), and I thought that it's about time to make the site more visible to search engines. Not being happy with several frameworks that I could use to this end (among them Struts 2, Rails and Grails - I will talk later more about this), I just googled a couple of months ago the Web for "restful urls" in a hope that I would find other emerging technologies capable of doing what I wanted - quite quickly I came across Restlet Web site.
Restlet framework turned out to be a lot more than just an API to use URLs I wanted. In a nutshell, it's full blown REST engine. Now, if you do not know what is REST, go and read the Roy Fielding's dissertation, Architectural Styles and the Design of Network-based Software Architectures. Or, at least this Wikipedia article on Representational State Transfer (that's what REST stands for).
Since the World Wide Web is the key example of a RESTful design, and Restlet framework is the REST engine, obviously, it represents an alternative to Servlet API - essentially the only (up until recently) option for Web development using Java platform. I am not going to debate here the issue of Servlets vs. Restlets. All I can say is that my experienced showed to me that Restlet API (currently at level 1.0.4) is a very viable substitute to Servlets. Things have changed.
Read the article to find more.
09/05/2007 by Serge Ilyn
1 2