> I do not think these names are being generated on the fly. I think the
designers actually created a separate asp page for each of their products,
using the naming convention to identify them.
I think it's plausible that it was a combination of manual/on the fly.
Consider a normalized schema where each unique product has exactly one row
in a view, it would be trivial to write a "page generator" that created a
page (folder/page name based on specific properties) with the page content
from the view; one page per product.
An admin page could be constructed to either (a) rebuild the entire set of
pages, or (b) take a specific product ID and rebuild just that one.
Sometime I should show you the ASPFAQ admin interface; one of the tasks the
final save page has when updating/adding an article is that the RSS XML file
is rebuilt (rather than have that page generated on the fly when it is
requested, it is static until it needs to change). At one point it also
built a static HTML file for just that article, but I ditched that feature.
This wouldn't necessarily have to be done by ASP either, but this is useful
if you want to handle the updates on demand along with the other updates.
If you want to schedule it (e.g. build all the pages once a day,
incorporating the day's changes), you could use something else (e.g. C#).