I enthusiastically endorse the idea of loose coupling between client and server; Restlet does this well and makes it easy to achieve complex mashups with minimal, very clean code.
Serving compiled GWT applications out of a Restlet container is definitely something we do often at work. The pattern does work under commercial shared Servlet containers, but I have not found these very commercially viable due to reliability issues and restrictions. (You kind of get what you pay for) I prefer to run Restlet instances directly in a virtual private server or in sandboxed VMs on a dedicated server if the budget allows. Restlet documentation is a big priority right now. Since the 1.0 release, a lot of documentation has been added, but also a lot of new extensions have been added (JAX-RS, GWT ...) Writing examples and tests, and documenting all the new stuff in 1.1 so that people other than Restlet wizards can easily jump aboard, will keep many of us busy for months to come. BTW, i think Restlet is exiting, so does GWT-1.5. Is there any example > to show server-side Restlet JSON service, even better to integrate with > GWT 1.5 JSONP using Java overlay? My strategy is to separate client-side > and server-side services so my server is only 1 of many possible service > sources for GWT mashup, where GWT application is compiled and served > under directory resource of Restlet under a Servlet engine available at > hosted sides such as GoDaddy. Is it a recommended practice? I can take > criticism so please share your experience. >
