Andreas Junghans <[EMAIL PROTECTED]> writes: > Of course, browsers and proxies don't specifically look for "nocache" in the > URL - the parameter could also be named "foobar" and have the same > effect. The way it works is that this parameter has a different value each > time, so that the URL is unique and never leads to a cache hit. I'm not sure > about today's implementations, but in the past, this was sometimes the only > reliable way to avoid caching.
Ok, that makes perfect sense. That means I have to leave setParameter() always putting parameters in the URL even if POST, which means I'll need another property for adding form fields. That's reasonable, I think, and is more flexible. > I think it's a good idea to add Pragma and Cache-Control headers, but please > don't remove the nocache parameter. Sounds good. Wilco. Derrell ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
