Scott Rotondo wrote:
Speaking of hidden assumptions, it's worth explicitly stating that my
implementation was designed to satisfy two requirements (admittedly
without satisfying the unknown constraint above):
R1. Existing URL's should be redirected to the corresponding page in the
new hierarchy if the new URL is valid.
R2. Pages that do not exist in the new hierarchy should be redirected to
the top-level page for their community or project.
Yes, I understood exactly what you were doing in your example.
While I suppose others could disagree, in my opinion R1 is *much* more
important than R2. Here's why this matters: If we drop requirement R2, I
think you'll agree that it's trivial to satisfy R1 (even in the presence
of constraint C1) using mod_rewrite or even using the simpler mod_alias.
In principle it is simple but with approximately 10k redirects, we'll
have to make sure that there aren't performance problems. Although the
current portal is going away Jive isn't, and Jive sits behind the same
Apache instance that will be doing the redirects. And we also have to
deal with the 13 country portals, which are also served from the same
Apache instance.
--
Alan Burlison
--
_______________________________________________
website-discuss mailing list
[email protected]
