Simon Reinhardt <simon.reinhardt <at> koeln.de> writes: > 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
Thanks Simon, So in an ideal world where one's IT budget was larger than management have given you would have a dedicated restlet 'box' serving only restlets on port 80. The problem i have is that i am constrained to one physical server which has apache on 80, glassfish on 8080 and 8181 and now i need to set up the restlets on another port. I tried many moons ago to get apache to pass through to glassfish on certain uri-stems but i ended up punching to death three monitors in thr process. now i just use the :<port> in the client uri. don't like doing it though as it exposes your architecture to evil-doers. Perhaps using the servlet as aproxy is the best way forward.. thanks hugh
