The answer (I think) is "well...... hmm...... kinda.. but not really"
The problem is links.
You might be able to 'hide' the first entry point. Instead of 'redirecting', you might be able to accomplish a server-side forward. Such that
www.foo.com/home would be a
servlet that actually invokes something hideous like
www.foo.com/home/servlet/blah?foo=1&bar=2 But what about the "next" step?
You can make your HTML *look* pretty, the text of the link can say anything, but the ACTUAL link must still point to
www.foo.com/home/servlet/anotherservlet?with=more&cruff=here The answer in this case, is to 'hide' the fact you are invoking a servlet.
Perl junkies love doing this. And it's possible in
Java as well, expecially if you don't mind parsing the results of calling getRequestURL(), getRequestURI() or even getPathInfo()
So you'd parse something "nice" looking like
www.foo.com/home/a/b to mean:
www.foo.com/home/servlet/blah?foo=a&bar=b But in the end.. *something* has to tell your application what to do.