Alan Burlison wrote:
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.
We have reviewed this in more detail and are proposing the following:
1) We make a full 1:1 mapping of all the old pages on the site to any
new pages that are being migrated to XWiki, so typing in
http://www.opensolaris.org/os/community/zfs/boot/zfsbootFAQ/
will go to:
http://hub.opensolaris.org/bin/view/Community+Group+zfs/zfsbootFAQ
2) The list will be cleaned up periodically to remove 404s (i.e.
zfsbootFAQ on hub gets deleted) and links with no traffic (no hits to
the destination page in 12 months).
3) There will be no second redirect. If the page moves, it results in a 404.
4) We can add additional links, on as needed basis, if they are
published in book or product readme. However, we ask that teams migrate
any product links as soon as feasible after the transition.
There will be performance hit from doing this, so we are planning to run
some tests on a stage implementation to gauge what the impact will be.
Derek
--
Derek Cicero
Program Manager
Solaris Kernel Group, Software Division
_______________________________________________
website-discuss mailing list
[email protected]
