Hi Hugh Hugh Acland wrote:
Is this not a weird thing to being doing, seeing as RestLet was supposed to be a better way of doing what a lot of people were using servelets for. The only reason I can think of for doing this would be a quick'n'easy way to "deploy" a restlet onto a specific addressable URI. What other benefits could there be?
As far as I know this is really just a deployment thing. In some environments you might already have a Servlet Container blocking port 80 so you can't just directly bind your Restlet app to that port. Instead you need to use the Servlet Container as a proxy. You have the same problem btw if you want to use, say, Tomcat for serving some things from a domain where Apache already hogs port 80 (unless you are fine with using anothert port). Hence the Apache JServe Protocol. The nice thing however is that you can write your app against the Restlet API and adjust the whole deployment scenario in one class. Simon
