thanks for your prompt reply. I am still a bit puzzled, can you elaborate it a bit more? If I call the encodeURL() in servlet, what happen when the browser support the cookie?
I (almost) agree. That would be actually nice, if I had control of the requirements / specs. At the moment I have to check the feasibility of the other option, regardless of the known side efects (performance, static pages,...)..
If I cannot do that, it's fine. But I need to be sure I can't achieved that (for example, looks like there are some setting in Bea and Tomcat to disable cookies but I wonder if the same result can be achieved programmatically, I don't like to be you vendor dependent)
I miss the old days when I would think up a sinister scheme for world domination and you would show a little emotional support. So just look at this tiny ad: