Re: [WebDNA] Cacheing include files

This WebDNA talk-list message is from

2015


It keeps the original formatting.
numero = 112187
interpreted = N
texte = Brian If the .frag file is only ever to be included and displayed in an HTML = file why don=E2=80=99t you use a SHOWIF. At the top of the HTML a TEXT var i.e. [TEXT]SHOWFRAG=3DT[/TEXT], then = wrap the contents of the .frag=20 [SHOWIF [SHOWFRAG]=3DT] FRAG CONTENTS [/SHOWIF] Then if the .frag file is ever served the content will be nothing. Kind regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au > On 17 Mar 2015, at 09:37, Brian Burton wrote: >=20 > Ken, >=20 > 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 >=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 >=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? >=20 >=20 > -Brian B.=20 >=20 >=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 >=20 >=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 Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Cacheing include files (Donovan Brooke 2015)
  2. Re: [WebDNA] Cacheing include files (Stuart Tremain 2015)
  3. Re: [WebDNA] Cacheing include files (Brian Burton 2015)
  4. Re: [WebDNA] Cacheing include files (Kenneth Grome 2015)
  5. [WebDNA] Cacheing include files (Brian Burton 2015)
Brian If the .frag file is only ever to be included and displayed in an HTML = file why don=E2=80=99t you use a SHOWIF. At the top of the HTML a TEXT var i.e. [text]SHOWFRAG=3DT[/TEXT], then = wrap the contents of the .frag=20 [SHOWIF [SHOWFRAG]=3DT] FRAG CONTENTS [/SHOWIF] Then if the .frag file is ever served the content will be nothing. Kind regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au > On 17 Mar 2015, at 09:37, Brian Burton wrote: >=20 > Ken, >=20 > 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 >=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 >=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? >=20 >=20 > -Brian B.=20 >=20 >=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 >=20 >=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 Stuart Tremain

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:

Formatting Email (2000) If search results are blank... (2003) W* 3.x & WebCat + WebMerchant (1998) [carts] and databases (1997) Clickable maps and WebCatalog? (1996) Great product and great job ! (1997) WebCat2b13MacPlugin - [math][date][/math] problem (1997) Cookies (1999) PIXO support (1997) Webcat OSX (2001) Error: the 'showcart' command requires that you specify a db (1997) [WebDNA] Dynamic vertical columns (2008) [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (2012) Adding muliple sku + quantities (1999) HTML editing and webcatalog (2000) different ship dates and shopping carts -- how to? (1997) OSX Applescripts -- Anyone? please? (2004) Browser Check for WebDNA compatability (1999) NT vs Mac (1997) RequiredFields notes ... (1997)