--- Dick Applebaum <[EMAIL PROTECTED]> wrote:
> At 10:03 PM -0700 7/27/00, Patrick Trongo wrote:
>
> >Questions...
> Are these, in fact hundreds of unique templates...
- Yes! this site has tens of thousands of dynamically generated pages that are
cached
the site uses a methodology that is componenet basesd (like Fusebox) as a matter of
fact 95% of
the site is generated through a single template...sound familiar?
> I use CF qyery caching & under most situations the dynamic pages
> outperformed he static pages.
>
> This is definitely the way to go... some other advantages are:
>
> pages are never out of date awaiting the next generation cycle:
> site is never unavailable while the new static pages are being installed
- Story server works as a 404 handler... the web server checks the file system for
the requested
URL, if it doesn't exist it passees the request on via 404 to Story server which then
creates it
on the fly. I think the speed of the cached system is based on the fact that it never
involves
story server after the pages are cached. But pages are always "available" just at a
speed cost.
>
> an entire operational process, the generation and installation of static
> pages, is entirely eliminated
- I towed that line also, but its hard to argue that that is necessary. If your
content
changes once a day, and you have 600,000 hits to a particular page.. why would you
want to create
that page 599,999 more times than you need to?
> Having a dynamic process in place promotes much better content, much more
> interactive site design, and much cleaner operation... it creates
> a different
> "mind-set" for everyone involved... you can make a few changes and they are
> immediately reflected in the entire system
- Thats my argument for CF... although the StoryServer mindset is very much
Dynamic page
generation...but only when absolutly needed. I was at cfug that Ben Forta Spoke at
recently.. this
was basically his message at the meeting. Don't continue to stress the CF boxes just
because you
can. There are much better processes the servers can be handling than recreating a
virtually
static page dynaically. As to the cascading effect of code changes... StoryServer can
do that, but
you must manually clear the Cached pages that are affected, but the end result is the
same... if
you change the graphic in the footer template and dump the cach, all of the pages now
will be
regen in sequence, or when requested with the new image. I am actually working on a CF
based
equivelent to StoryServer. I like the Caching Scheme, it makes sense. CF Scheme
doesn't have the
404 handler benefit that SS has... don't know exactly how to handle that... your
issues are all
valid in the CF environ.
> the whole page/program organization/maintenance issue is orders of magnitude
> simpler... you just don't have all these thousands of pieces of crap laying
> around... taking up your space/time/attention
>
Thanks!
=====
Patrick Trongo
Sr Programmer/Analyst
4Anything Network (www.4anything.com)
487 Devon Park Road Suite 204
Wayne, PA 19087
Telephone: 610-768-1444 Ext 204
Fax: 610-592-1094
__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
