Re: Database flushing does not work any more...
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 29831
interpreted = N
texte = >Joe, I think you are confusing no-cache directives with flushing templates >from cache. The no-cache directives are just [setMIMEheader] commands added >to the admin templates to keep browsers from caching the templates, which >can cause problems when updating preferences. This addition is really not a >bug fix per se. In fact it is just a modification of the html pages in the >admin folder within the webcatalog folder, and not a change in Webcatalog's >internal code.That all depends on what your definition of is is.Thank you for your definition of a bug. The original poster was, I believe, talking about the problem with the admin templates whereby if you click on the Flush Databases hotlink or the Commit and Close all Databases hotlink, nothing would actually get closed or flushed and that was because the web server's response may have already been cached in the browser. And the point is that while there may not be an error in the server software that is loaded in my computer's RAM... there was a problem with the tools that are delivered that configure the software.If there wasn't a problem, I guess SM didn't need to fix it.___Joe___ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
Associated Messages, from the most recent to the oldest:
>Joe, I think you are confusing no-cache directives with flushing templates >from cache. The no-cache directives are just [setmimeheader] commands added >to the admin templates to keep browsers from caching the templates, which >can cause problems when updating preferences. This addition is really not a >bug fix per se. In fact it is just a modification of the html pages in the >admin folder within the webcatalog folder, and not a change in Webcatalog's >internal code.That all depends on what your definition of is is.Thank you for your definition of a bug. The original poster was, I believe, talking about the problem with the admin templates whereby if you click on the Flush Databases hotlink or the Commit and Close all Databases hotlink, nothing would actually get closed or flushed and that was because the web server's response may have already been cached in the browser. And the point is that while there may not be an error in the server software that is loaded in my computer's RAM... there was a problem with the tools that are delivered that configure the software.If there wasn't a problem, I guess SM didn't need to fix it.___Joe___ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
Joseph D'Andrea
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Ampersands in database fields? (1998)
ftp access on Macos X (2000)
Re(6): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (1998)
problems with 2 tags (1997)
Text limits in NT version? (1997)
Shipcost lookup? (1997)
shortening the cart (1998)
New user...saying thanks, and whaddayathink? (2000)
Generating Report Totals (1997)
[WebDNA] PDF's on the fly from a webdna database (2009)
Databases.tpl (2000)
Running 2 two WebCatalog.acgi's (1996)
showing *all* name/value pairs with [search] (2003)
bannerads example idiot (1997)
Cold Fusion Buster (1997)
faxing orders (2000)
Cookies (2003)
Beta 3.0.3 fix for serial# problem (Mac) (1998)
Bug? (1997)
webcat2b12 CGI -- Date comparisons (1997)