This is a purely theoretical observation and not really meant as an answer, but I did want to sort of get it on the record here. The MVC paradigm is a specific separation of concerns architecture which has gained wide conceptual support because it has long been generally considered best practice for GUI applications. Overlaying MVC onto the internals of a RESTful web application may encourage correct separation of concerns, but also may not. MVC alone does not capture separations of concern at multiple layers of an n-tier application.
REST works very well with a rich client (GWT, Flex RIA, SWT, Swing...) that has its own complex UI, ideally implemented using the MVC pattern. As Thierry says, the internals of a Restlet application can be composed using an MVC way of thinking. Here, though, the MVC pattern is not an automatic best practice and you may do better to just study the concerns in your server and leveraging the concepts in Restlet (which in turn are REST concepts) without reference to MVC. Fielding mentions MVC in passing in his REST dissertation, when surveying preexisting peer-to-peer architectures, but REST itself is not based on an MVC way of thinking. I would argue that there is not a "correct" way of implementing MVC in Restlet ... it's just that if you choose to think about server-side things this way, there are ways (as Thierry outlines) of accomplishing this. Personally, I would set aside thinking about MVC on the server, in favor of thinking purely about REST. I tend to find the MVC switch in my brain only activates when writing client side code, where it is ideally suited. You may get widely divergent opinions on the list, but that is mine! :-) - Rob On Fri, Nov 21, 2008 at 2:09 AM, Gan123 <[EMAIL PROTECTED]> wrote: > > > i am creating a web application using Restlet based on MVC. i have > configured ServlerServlet to invoke my Application class, where i have all > the URI mappings. i am planning to use the Application class as controller > and Resource to implement business logic with other required patterns. > > can any one suggest me whether this is the correct way to go ahead to > implement MVC application in RESTlet? how and when the Application will be > loaded? is it for every request or once per application ? > > Thanks in advance. > -- > View this message in context: > http://n2.nabble.com/Restlet-MVC-tp1560691p1560691.html > Sent from the Restlet Discuss mailing list archive at Nabble.com. > >
