Hi Adam, Thanks for reaching us and your interest in Restlet :)
[1] The Jetty connector is production ready and much lighter than a full Servlet container. [2] It is still a work in progress. Not sure to get this ready for RF 2.2 at this point. We need help on the documentation front mostly as most of the code has already been upgraded to the OAuth 2.0 final RFC. [3] Yes, it is possible using the callback mechanism. See this method: http://restlet.org/learn/javadocs/snapshot/jee/api/org/restlet/resource/ClientResource.html#setOnResponse(org.restlet.Uniform) Best regards, Jerome -- http://restlet.org http://twitter.com/#!/jlouvel 2013/4/8 Adam Mc <a...@cs.miami.edu> > This is my fist message on the restlet discussion. First, I just want to > say thanks to the developers of Restlet. It seems like a great api and > framework. We are evaluating Restlet, and we have a few general questions. > I apologize if the questions are a bit diverse, but I thought I would > just send them in one message. > > [1] Jetty Connector vs Servlet Container: We would like to use the Jetty > connector as a standalone outside of a servlet container. Is Restlet > standalone with Jetty as stable as using a servlet, or is a servlet > container preferred for production? > > [2] The book mentions that Oauth 2.0 is in draft. Is Oauth 2.0 nearing > production code? Not rushing, just wondering? > > [3] Is there any way to handle Ascynhrous Client requests. Considering > that our webserver is also a client to other servers, the client needs to > consume other restful services. Is there anyway to consume services in a > non blocking or ascyh manner, so as to not keep the threads blocking. If > so, can someone point me into the direction of code example. > > Thanks, > > -Adam > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3052727 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3054131
