Martin Lew <[EMAIL PROTECTED]> writes: > << > Oh dear. Didn't you say you were having trouble with the image? > >> > > Like I said clearly in the first message, I have my image correctly the > first time so the problem is not the image generation but the cache of > Tomcat. I tested all with Firefox and I'm sure that is not Apache or any > browser the problem, I did tests that proves me that it was Tomcat the problem. > I just want to know if someone know how to "play" with the cache settings in > Tomcat. > (I agree that is maybe not the right place to post after reflexion but > people here seem to be more serious than a lot of others place, so I have > more chance to meet an expert of this kind of questions).
The reason I was getting frustrated with you is that Tomcat does not have a cache. You are wrong when you say that it does. HTTP has a caching system, which you may be using (perhaps without realizing it). In order to know that we have to see the source code for the servlet that sends the image responses. Lastly, this statement amuses me: > I did tests that proves me that it was Tomcat the problem. I strongly suspect it's your code and your understanding of caching that is the problem. It's always tempting when you have a frustrating problem, to blame it on the container, the webserver, the operating system, whatever. The temptation to believe that you have discovered a bug is tremendous and almost universally wrong /8-> -- Nic Ferrier http://www.tapsellferrier.co.uk ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
