Re: [WebDNA] Cacheing include files
This WebDNA talk-list message is from 2015
It keeps the original formatting.
numero = 112186
interpreted = N
texte = Ken, I=E2=80=99m doing Ok on writing out the fragments, and using them as = [include]=E2=80=99d content as needed. I do not write out a whole page = of html because I have personalized dynamic content on other parts of = the page.=20 The concern is have is, and why i don=E2=80=99t want this mapped as a = template is that the webserver will serve up template files when = requested. i.e. if you have storefunctions.inc as a file, and someone is = savvy enough to request it, either it isn=E2=80=99t mapped to webdna, = and Apache happily serves up your raw webdna as text to who ever ask for = it (bad) or if it is mapped, then webdna will try to run any embedded = code and then return it to Apache to show to your malicious visitor. = What I want/need is an extension that webdna can cache, and yet that = Apache ignores, or refuses to acknowledge exists.=20 I feel like I=E2=80=99m overlooking something, but I haven=E2=80=99t had = enough time to dig in and find a good solution. Has anyone solved this = already? -Brian B.=20 > On Mar 16, 2015, at 4:45 PM, Kenneth Grome
= wrote: >=20 > I would write a WebDNA script that runs automatically once a day > (via cron, trigger, etc.) and writes complete .html files, one for > every author, overwriting whatever matching files were already > there. Then you know for a fact that all these pages are > up-to-date as of today, and WebDNA never has to do any of the hard > work at the time the visitor actually requests one of these pages. >=20 > If you don't like this idea and instead you actually want WebDNA > to cache your .inc and .frag files you can change their suffixes > to one that WebDNA is already processing, or add .inc and .frag to > your WebCatalog "ValidTemplateExtensions" preference and to the > "AddHandler webcatalog2-handler" directive in Apache's webdna.conf > file. >=20 > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Management >=20 >=20 > On 03/16/2015 02:04 PM, Brian Burton wrote: >> Greetings! >>=20 >> 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) >>=20 >> 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=E2=80=99s 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. >>=20 >> SO.. here=E2=80=99s 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? >>=20 >> Thanks! Brian B.=20 >> --------------------------------------------------------- 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 >>=20 > --------------------------------------------------------- > 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 >=20
Associated Messages, from the most recent to the oldest:
Ken, I=E2=80=99m doing Ok on writing out the fragments, and using them as = [include]=E2=80=99d content as needed. I do not write out a whole page = of html because I have personalized dynamic content on other parts of = the page.=20 The concern is have is, and why i don=E2=80=99t want this mapped as a = template is that the webserver will serve up template files when = requested. i.e. if you have storefunctions.inc as a file, and someone is = savvy enough to request it, either it isn=E2=80=99t mapped to webdna, = and Apache happily serves up your raw webdna as text to who ever ask for = it (bad) or if it is mapped, then webdna will try to run any embedded = code and then return it to Apache to show to your malicious visitor. = What I want/need is an extension that webdna can cache, and yet that = Apache ignores, or refuses to acknowledge exists.=20 I feel like I=E2=80=99m overlooking something, but I haven=E2=80=99t had = enough time to dig in and find a good solution. Has anyone solved this = already? -Brian B.=20 > On Mar 16, 2015, at 4:45 PM, Kenneth Grome = wrote: >=20 > I would write a WebDNA script that runs automatically once a day > (via cron, trigger, etc.) and writes complete .html files, one for > every author, overwriting whatever matching files were already > there. Then you know for a fact that all these pages are > up-to-date as of today, and WebDNA never has to do any of the hard > work at the time the visitor actually requests one of these pages. >=20 > If you don't like this idea and instead you actually want WebDNA > to cache your .inc and .frag files you can change their suffixes > to one that WebDNA is already processing, or add .inc and .frag to > your WebCatalog "ValidTemplateExtensions" preference and to the > "AddHandler webcatalog2-handler" directive in Apache's webdna.conf > file. >=20 > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Management >=20 >=20 > On 03/16/2015 02:04 PM, Brian Burton wrote: >> Greetings! >>=20 >> 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) >>=20 >> 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=E2=80=99s 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. >>=20 >> SO.. here=E2=80=99s 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? >>=20 >> Thanks! Brian B.=20 >> --------------------------------------------------------- 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 >>=20 > --------------------------------------------------------- > 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 >=20
Brian Burton
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:
CSV import suggestions (2007)
Multiple prices (1997)
Need Sample Template - just purchased (1997)
WCS Newbie question (1997)
Can he do that? (1998)
Configuring E-mail (1997)
Getting Crazy (1998)
WebTen and WebCat (1997)
WebDNA 4.5.1 Now Available (2003)
FYI: virus alert (1996)
too many nested tags ... (1997)
No messages for a week? (2000)
Somebody to open my eyes!!! (2004)
Web Developer Product Awards (1997)
New public beta available (1997)
AOL refuses some e-mails (2000)
WebCatalog for Postcards ? (1997)
[WebDNA] WebDNA code validator (2011)
Initiating NewCart (1997)
WCS Newbie question (1997)