Re: Firesite cache vs webcat cache
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 15278
interpreted = N
texte = >>I was thinking of taking the firesite cache setting and changing >>it to zero and let webcatalog do it all. > >This is not a good idea, because FireSite makes lots of changes to >the document after WebCatalog hands off the HTML to it. Really you >want both. > >WebCatalog Cache: speeds up things like [include] and any template >processing, because WebCatalog won't have to go to disk to open >those files. > >FireSite Cache: speeds up links to URLs that FireSite deems are >identical, so it won't have to ask WebCatalog to process pages that >it's already done Grant, it doesn't seem like FireSite can use the creation date/time of a WebCat-rendered page when making its decision to re-render or to NOT re-render a previously-rendered page ...... so does FireSite make this decision by comparing the entire HTML of each page it gets from WebCat -- to see if that exact HTML has already been rendered by FireSite?Because if this is what FireSite does, then it would make sense to use as large a FireSite cache as possible ... right?Sincerely, Ken Grome WebDNA Solutions http://www.smithmicro.com/webdnasolutions/...
Associated Messages, from the most recent to the oldest:
>>I was thinking of taking the firesite cache setting and changing >>it to zero and let webcatalog do it all. > >This is not a good idea, because FireSite makes lots of changes to >the document after WebCatalog hands off the HTML to it. Really you >want both. > >WebCatalog Cache: speeds up things like
[include] and any template >processing, because WebCatalog won't have to go to disk to open >those files. > >FireSite Cache: speeds up links to URLs that FireSite deems are >identical, so it won't have to ask WebCatalog to process pages that >it's already done Grant, it doesn't seem like FireSite can use the creation date/time of a WebCat-rendered page when making its decision to re-render or to NOT re-render a previously-rendered page ...... so does FireSite make this decision by comparing the entire HTML of each page it gets from WebCat -- to see if that exact HTML has already been rendered by FireSite?Because if this is what FireSite does, then it would make sense to use as large a FireSite cache as possible ... right?Sincerely, Ken Grome WebDNA Solutions http://www.smithmicro.com/webdnasolutions/...
Kenneth Grome
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:
[SHOWIF AND/OR] (1997)
[INCLUDE] Limitations (1998)
Encrypt (1999)
Seed encrypt/decrypt code error or bug? (1999)
Some ThankYou page problems (1997)
[OT] (waaaay OT) further off topic than before (2004)
RE: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA Operations (2014)
Where's Cart Created ? (1997)
Internet Explorer and caching (2000)
Quit revisited (1997)
Searchable WebCat (etc.) Docs ? (1997)
WebCatalog2 for NT Beta Request (1997)
[WriteFile] problems (1997)
webcat2b12 CGI -- Date comparisons (1997)
method of payment (1997)
Include files (1998)
Tax & Shipping (1997)
New WebCatalog site! (1997)
Re[3]: 2nd WebCatalog2 Feature Request (1996)
RE: too many nested [xxx] (1997)