audiopro
Those pages are static pages - not dynamically created. Search engines do a horrible job of indexing dynamic pages and when they do they cannot seem to serve up the same page twice using the same search terms. When my customers do a search they want the same page to come up every time, not one page to be cached and different one show when refreshed.
Not only that, but dynamic pages load slowly. I have a competitor that dynamically generates pages using PHP and it is very irritating waiting 10-20 seconds for PHP to generate the page and serve it up on a cable connection. The average load time (according to Google) of my pages is under 1 second per page.
And I have no problem with my sanity when it comes to those pages. I wrote a FoxPro program which generates them from a database including everything needed for them to function correctly. Generation plus uploading time is around 1400 pages per hour on a dialup connection. I could do the same thing with CSS, but it will not happen in the near future, if ever.
25% of the hits on my pages are from NS4/IE5 and earlier. It is much easier to use frames since almost every browser serves them up the same way using the same code. Not so with any other method I know of.
Soon I will be making a 'minor' improvement to the pages to limit the number of pages regenerated to keep from regenerating pages that have not changed. When I do that, frames will be far the best solution since I can keep the hundreds of menus totally separate from the thousands of pages. Not using frames would require regenerating hundreds of pages where only the menu changed and none of the content changed or would require using some kind of server side scripting to keep the menus updated, neither of which is a good option for me.
mmerlinn
"We've found by experience that people who are careless and sloppy writers are usually also careless and sloppy at thinking and coding. Answering questions for careless and sloppy thinkers is not rewarding." - Eric Steven Raymond