Re: [WebDNA] Pretty URLS
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106579
interpreted = N
texte = All I'm saying is that it takes zero WebDNA processing to serve static pages ... And the resources required to generate a few hundred thousand static pages is a few seconds -- once a day -- which can be done by spawning the task so visitors are never slowed down by it even if it were to take several minutes. What you're suggesting requires the server to use WebDNA for every single request, and with "hundreds of thousands" of records to search upon each request you're going to substantially increaase the load on WebDNA. No problem if WebDNa can keep up with it. Then again, if anything should happen to your WebDNA templates or to WebDNA itself your whole site will come grinding to a halt -- because you have no static pages for the search engines to continue to visit while you're fixing the WebDNA problem. Of course you can do whatever you like, I'm just pointing out that there are significant benefits (to me anyways) by writing a script that creates/updates a simple set of specially designed static search engine pages every day -- without my ever having to think about it. To each his own! :) Sincerely, Kenneth Grome P.S. I consider a few hundred thousand static pages to be exceptionally clean and simple, not messy at all. But maybe it's just me who thinks like this. > the website in question sells replacement parts, so skus > = couple thousand. Things they fit into = couple > hundred thousand. Oh, and people google search for the > thing the parts fit into. So I'd have a few hundred > thousand static pages, which although automated, is > still quite messy.
Associated Messages, from the most recent to the oldest:
All I'm saying is that it takes zero WebDNA processing to serve static pages ... And the resources required to generate a few hundred thousand static pages is a few seconds -- once a day -- which can be done by spawning the task so visitors are never slowed down by it even if it were to take several minutes. What you're suggesting requires the server to use WebDNA for every single request, and with "hundreds of thousands" of records to search upon each request you're going to substantially increaase the load on WebDNA. No problem if WebDNa can keep up with it. Then again, if anything should happen to your WebDNA templates or to WebDNA itself your whole site will come grinding to a halt -- because you have no static pages for the search engines to continue to visit while you're fixing the WebDNA problem. Of course you can do whatever you like, I'm just pointing out that there are significant benefits (to me anyways) by writing a script that creates/updates a simple set of specially designed static search engine pages every day -- without my ever having to think about it. To each his own! :) Sincerely, Kenneth Grome P.S. I consider a few hundred thousand static pages to be exceptionally clean and simple, not messy at all. But maybe it's just me who thinks like this. > the website in question sells replacement parts, so skus > = couple thousand. Things they fit into = couple > hundred thousand. Oh, and people google search for the > thing the parts fit into. So I'd have a few hundred > thousand static pages, which although automated, is > still quite messy.
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:
WebCatb15 Mac CGI -- [purchase] (1997)
# of real domains on 1 web server (1997)
Passing Username and Password on the command line (2000)
WebCat2: Formulas.db question (1997)
For those of you not on the WebCatalog Beta... (1997)
RE: OK, here goes... (1997)
BUG?-.html extention not working. (2000)
[WebDNA] error on mirror site (2015)
Help with nested search (1998)
WCS Newbie question (1997)
referrer usage (1997)
hideif [x]=1,2,3.. (2003)
Location of Browser Info.txt file (1997)
[LOOKUP] (1997)
Prices coming up 0.00 (2001)
Date Search Problem (1999)
Extended [ConvertChars] (1997)
two unique banners on one page (1997)
OT-JS why it does not run on Mac (2001)
Warning: Mac OS X 10.2.4 Update Overwrites Apache's (2003)