On Aug 12, 2009, at 1:05 PM, Hugh McIntyre wrote:
Elaine Ashton wrote:
I AM thinking of the end users as if we would do a URI rewrite for
10-20,000 pages, this would entail the server scanning /every/ rule
to match against before finally serving up the page. In the battle
of glacial server vs. broken link on a zippy server, the zippy
server wins.
You could obviously do a database lookup to go from old->new, rather
than a log list of rewrite rules, for performance. For example in
mod_perl. The database of old->new conversion mappings gets created
once when the site is migrated.
And if the URL space is organized appropriately, you can make sure
that only old pages go through this database lookup, for example a
top level rule that this only kicks in for pages starting with /os/
(and not using this prefix for the new site).
Have you done this yourself on a high-traffic production-level
webserver?
e.
_______________________________________________
website-discuss mailing list
[email protected]