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 > À : discuss@restlet.tigris.org > 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
