Re: Firesite cache vs webcat cache
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 15279
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 donehmmm read that last line....already done!!!OK, but when I have a page that you get to via the hyperlink $search and then it looks upon it's self to do a shownext, if I do a sort based on as it gets confused and if I do a search on de it seems to work OK. But it has already done the same page/template right! Or did I misunderstand you above?Have the identical page created in 2 different places that show images only, in one the file names are 1,2,3,4,5, etc.jpg and the other it is H, 22b, goto27a, etc .jpg. And it first searches by a date that the image was added and then searches by file name. The one with no order to the file names sometimes looses the startat value where the other just cooks along. Keep in mind that on the one with numeric file names it is a duplicate search to be searching by add date. Since we generate the filename at the time it is added. meaning the newest files have the highest number and the newest date (so duplicate sort for both date and filename). And that is how they are displayed. Most recent by date and highest number file name first in sort value. Kill the browser, flush it's cache, don't touch the server and the one with the ramdon file names seems to work ok for a while and then it starts to loose the startat value. Where the one based on numeric file names has never shown this problem. And all I did was do a duplicate file of the first one and edit the template names.Pick up the same pages and files and move them to a none firesited site and it all seems to work OK. Remember the problem I posted last week where the [showif [form.bodytext]=] warn me it is empty [/showif] failed when it wasn't empty. Well I put it back in place and now it seems to work again. At least it did over the weekend and several entries. And trust me I know it failed when it should not have. The server box is a G3 (back side cache) and the client box is a Mach5 (inline cache), both running OS8. So either the server or the client box is loosing values. And I think it is the server box that is firesited. That is why I question the cache settings in the first place. Now I can always go back and quickly edit the file names that are random to numeric values since there are only 50 or 60 so images involved, displayed 12 on a page. Now this in not using the newest webcat beta which is pixo compliant if that would make any difference. I didn't put in place as planned over the weekend after reading some posts about people saying the speed dropped. And now on Monday nobody has said a word about this for days. Is 2.1b3 acgi safe to use?=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com ===============================================
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 donehmmm read that last line....already done!!!OK, but when I have a page that you get to via the hyperlink $search and then it looks upon it's self to do a shownext, if I do a sort based on as it gets confused and if I do a search on de it seems to work OK. But it has already done the same page/template right! Or did I misunderstand you above?Have the identical page created in 2 different places that show images only, in one the file names are 1,2,3,4,5, etc.jpg and the other it is H, 22b, goto27a, etc .jpg. And it first searches by a date that the image was added and then searches by file name. The one with no order to the file names sometimes looses the startat value where the other just cooks along. Keep in mind that on the one with numeric file names it is a duplicate search to be searching by add date. Since we generate the filename at the time it is added. meaning the newest files have the highest number and the newest date (so duplicate sort for both date and filename). And that is how they are displayed. Most recent by date and highest number file name first in sort value. Kill the browser, flush it's cache, don't touch the server and the one with the ramdon file names seems to work ok for a while and then it starts to loose the startat value. Where the one based on numeric file names has never shown this problem. And all I did was do a duplicate file of the first one and edit the template names.Pick up the same pages and files and move them to a none firesited site and it all seems to work OK. Remember the problem I posted last week where the [showif [form.bodytext]=] warn me it is empty [/showif] failed when it wasn't empty. Well I put it back in place and now it seems to work again. At least it did over the weekend and several entries. And trust me I know it failed when it should not have. The server box is a G3 (back side cache) and the client box is a Mach5 (inline cache), both running OS8. So either the server or the client box is loosing values. And I think it is the server box that is firesited. That is why I question the cache settings in the first place. Now I can always go back and quickly edit the file names that are random to numeric values since there are only 50 or 60 so images involved, displayed 12 on a page. Now this in not using the newest webcat beta which is pixo compliant if that would make any difference. I didn't put in place as planned over the weekend after reading some posts about people saying the speed dropped. And now on Monday nobody has said a word about this for days. Is 2.1b3 acgi safe to use?=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com ===============================================
grichter@panavise.com (Gary Richter)
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:
security (1997)
Signal Raised (1997)
WebDNA Solutions ... sorry! (1997)
Modifying order output (1997)
RE: problem with applets embedded in tpl files (1997)
RE: Database field limit? (1998)
Sorting... stumped. (2006)
Date search bug (1998)
webcat 2.1 new cart fields - please explain more (1998)
Sorting problem (2002)
Subtotal Not Calculated on Invoice.html (1998)
Exclude by date - multiple (1997)
SiteBuilder Problem (2004)
Dummy Credit Card Number for debug? (1997)
WebCat2b13MacPlugIn - [shownext method=post] ??? (1997)
Bug or syntax error on my part? (1997)
Re:2nd WebCatalog2 Feature Request (1996)
[ot] Securing PHP & MySQL (2003)
RE: Personal Web Server combined with Webcatalog 2.1 (1998)
AutoCommit Preference? (1998)