From: Bill Skellenger <wskellenger@sp...> - 2003-09-11 02:33:47
On one hand I'm not sure if this is necessary for my site... It is
running behind a firewall on our company's intranet. Currently it is in
a proof-of-concept phase serving as a department webpage in order to
improve our information sharing and access. I doubt that the number of
hits the page will receive in a day will be anywhere near what a similar
site on the internet might receive. However, once deployed, it may
receive a fair number of hits from other departments... And then if our
counterparts in Germany and Japan decide to use it, who knows...
So I guess for my problem -- only users with a certain seclev can access
section xxx -- it would be useful to disable writing to shtml for stores
in those restricted sections only. OR, the stores can still be written,
but only the intro text and not the full aritcle for those stories...
Just kind of thinking out loud...
Thanks for your response,
>There are a number of very good reasons. First, if your database is down
>or overloaded you can set the panic_level to 2 and all content will be
>served from the static files. Then, non-registered users can be always
>served the index.shtml static homepage, with links to static pages, with
>big saves in terms of CPU cycles. Since web spiders are just like
>anonymous users, these files are also the best targets for Google and