I'll second Serge's feedback on the documentation. A user guide would be nice, but I'd argue that having accurate and useful javadoc would be much, much more helpful.
For example, a coworker was implementing something that handled PUT - he overrode handlePut() instead of put(). Looking at the Javadoc, its not clear why you would use one vs. the other. In fact, without looking at the code, I have no idea why you would use one over the other. There are dozens of other examples I could give - there are just too many entries where the description is simply just a restatement of the method name with no clue how it relates to anything else. It would also be useful if there were more explicit references to HTTP instead of just using the generic REST terminology. Often, the REST terminology is way too vague - when I'm trying to interoperate with someone else, I'm operating at the HTTP level, not the REST level, so I need to know precisely what impact various methods have on request or response methods. For example, it would be nice if Response.setRedirectRef actually said that it sets the Location header and whether it does anything else. --Chuck -----Original Message----- From: Jerome Louvel [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 15, 2007 1:33 PM To: [email protected] Subject: RE: two quick questions Hi Serge, You're welcome! Thanks for your patience in solving your routing issue. We know that a detailed user guide is missing in our documentation. We hope to start filling this hole at the end of the year. Thanks also for the positive comparison against other frameworks. If you see anything missing for your requirements, please feel free to share them, we are always looking for improvements ideas. BTW, the Restlet project is composed of a Restlet API, a reference implementation (called Noelios Restlet Engine, NRE), and a set of extensions. The whole package is considered as a framework. Best regards, Jerome > -----Message d'origine----- > De : news [mailto:[EMAIL PROTECTED] De la part de serge Envoyé : > mercredi 15 août 2007 19:16 À : [email protected] Objet : Re: > two quick questions > > > This should definitely work! :)Regards,Jerome > > > Hi Jerome, > > Thank you very much for helping - your suggestion helped, and it's > working as expected. I also would like to give a quick feedback. I > looked at messages on the board - a lot of people here are interested > in RESTful alternative to web services. I am primarily evaluating this > API (at least at this moment) as an alternative to building Web sites > with "cool" URLs (this also explains why I pay special attention to > anything that relates to this issue). I have gone already through a > number of frameworks that can do this (including Struts2/Webwork, > Rails, etc). I should say, so far from what I've seen and my attempts > to implement complex site designs, Restlet API (why you call it a > framework?) is the best option for various reasons. As far as this > thread is concerned, I can only say that just reading API javadocs I > would have probably never figured out how to solve the problem, and I > would have ended up with going through the source code. So, your help > is certainly appreciated. > > Best regards, > Serge
