Re: [WebDNA] Cacheing include files

This WebDNA talk-list message is from

2015

It keeps the original formatting. numero = 112185
interpreted = N
texte = I would write a WebDNA script that runs automatically once a day(via cron, trigger, etc.) and writes complete .html files, one forevery author, overwriting whatever matching files were alreadythere. Then you know for a fact that all these pages areup-to-date as of today, and WebDNA never has to do any of the hardwork at the time the visitor actually requests one of these pages.If you don't like this idea and instead you actually want WebDNAto cache your .inc and .frag files you can change their suffixesto one that WebDNA is already processing, or add .inc and .frag toyour WebCatalog "ValidTemplateExtensions" preference and to the"AddHandler webcatalog2-handler" directive in Apache's webdna.conffile.Regards,Kenneth GromeWebDNA Solutionshttp://www.webdnasolutions.comWeb Database Systems and Linux Server ManagementOn 03/16/2015 02:04 PM, Brian Burton wrote:> Greetings!> > What is the WebDNA community doing for cacheing page fragment> files? On my website I have some pages that require significant> processing to generate the visible content. To save time, I> only render it out the processing intense parts once an hour or> day or whatever (as required). I save this out as a fragment of> HTML in a file (with an .inc or .frag extension)> > An example of this might be a database of books, and I need to> create a page that has as html links, a list of unique authors> and a count of books attributed to that author. Rather then do> this every time the page is requested, i first check to see if> the fragment exists, then check to see if it’s current, and> then if both of those are false I render out the html, save it> in a new fragment file, and display it to the user.> > SO.. here’s my question: the fragments are saved as .inc or> .frag. WebDNA does not cache these as they are neither> templates nor databases. This causes a lot of disk activity as> I use fragments extensively to speed up the the quasi-static> parts of the website. How can I get webdna to cache these? I am> hesitant to add the extensions to the template field in the> settings. I do not want the fragment under any circumstance to> be able to be directly accessed by a web visitor. Should I> block the extension from being served by Apache? Would it be> possible to get a third cache field type in the webdna> settings? Thoughts? Suggestions?> > Thanks! Brian B. > --------------------------------------------------------- This> message is sent to you because you are subscribed to the> mailing list . To unsubscribe, E-mail to:> archives:> http://mail.webdna.us/list/talk@webdna.us Bug Reporting:> support@webdna.us> Associated Messages, from the most recent to the oldest:

Re: [WebDNA] Cacheing include files (Donovan Brooke 2015)
Re: [WebDNA] Cacheing include files (Stuart Tremain 2015)
Re: [WebDNA] Cacheing include files (Brian Burton 2015)
Re: [WebDNA] Cacheing include files (Kenneth Grome 2015)
[WebDNA] Cacheing include files (Brian Burton 2015)

I would write a WebDNA script that runs automatically once a day(via cron, trigger, etc.) and writes complete .html files, one forevery author, overwriting whatever matching files were alreadythere. Then you know for a fact that all these pages areup-to-date as of today, and WebDNA never has to do any of the hardwork at the time the visitor actually requests one of these pages.If you don't like this idea and instead you actually want WebDNAto cache your .inc and .frag files you can change their suffixesto one that WebDNA is already processing, or add .inc and .frag toyour WebCatalog "ValidTemplateExtensions" preference and to the"AddHandler webcatalog2-handler" directive in Apache's webdna.conffile.Regards,Kenneth GromeWebDNA Solutionshttp://www.webdnasolutions.comWeb Database Systems and Linux Server ManagementOn 03/16/2015 02:04 PM, Brian Burton wrote:> Greetings!> > What is the WebDNA community doing for cacheing page fragment> files? On my website I have some pages that require significant> processing to generate the visible content. To save time, I> only render it out the processing intense parts once an hour or> day or whatever (as required). I save this out as a fragment of> HTML in a file (with an .inc or .frag extension)> > An example of this might be a database of books, and I need to> create a page that has as html links, a list of unique authors> and a count of books attributed to that author. Rather then do> this every time the page is requested, i first check to see if> the fragment exists, then check to see if it’s current, and> then if both of those are false I render out the html, save it> in a new fragment file, and display it to the user.> > SO.. here’s my question: the fragments are saved as .inc or> .frag. WebDNA does not cache these as they are neither> templates nor databases. This causes a lot of disk activity as> I use fragments extensively to speed up the the quasi-static> parts of the website. How can I get webdna to cache these? I am> hesitant to add the extensions to the template field in the> settings. I do not want the fragment under any circumstance to> be able to be directly accessed by a web visitor. Should I> block the extension from being served by Apache? Would it be> possible to get a third cache field type in the webdna> settings? Thoughts? Suggestions?> > Thanks! Brian B. > --------------------------------------------------------- This> message is sent to you because you are subscribed to the> mailing list . To unsubscribe, E-mail to:> archives:> http://mail.webdna.us/list/talk@webdna.us Bug Reporting:> support@webdna.us> Kenneth Grome

DOWNLOAD WEBDNA NOW!

Re: [WebDNA] Cacheing include files

2015

Top Articles:

Related Readings: