Why didn�t you choose to use the url rewriting session management?
Is it possible to generate a total unique session ID using the following code:
String uid = new java.rmi.server.UID().toString();
return java.net.URLEncoder.encode( uid );
all images on the website is "crushed out"
Are you applying the filter to images served by your site? You shouldn't do that. This filter should apply only to responses containing html -- content with urls.
Or is the problem that the filter is mangling the image urls?
I noticed that when i have a JSP page with jsp:include calls and images, the filter gets called for every include and image! Why is this? How do I stop this and make it called once for the entire page?
For my needs that would have been overkill. I simply needed a value that changed over time.
UID() returns a number guaranteed to be unique over time. A timestamp is not guaranteed to be unique. (Many pages could be generated within 1 millisecond and each would have the same timestamp in the urls.)
I haven't tried it, but I'm guessing that generating an id using UID().toString() would be slightly more CPU-intensive.
I read your post several times, and it seems to be an argument against using a timestamp, but you chose to use a timestamp. Why?
Another guy from this forum had the same problem with the filter