Giacomo Pati wrote:
>On Fri, 9 Aug 2002, Michael Wechner wrote:
>
>>Hi
>>
>>I have a situation where I would like to do a lot of
>>URI-redirects/rewrites. I know I can do this via the sitemap,
>>but other people would be doing this. So for the reason of "Separation
>>of Concern" I would like to separate this from the actual sitemap.
>>
>>My question is what are the possibilties to do something like that?
>>
>>-One way would probably be to have a separate sitemap dedicated to
>>redirects, which is mounted by the actual sitemap.
>>
>>-Or to have the redirects in a separate file, which is "pulled in" by
>>the actual sitemap as an external entity
>>
>>-Or to have an action/component, where every request is sent through and
>>is acting
>>as an redirect/rewrite module (and maybe calling Cocoon again!!)
>>
>>Any thoughts on this?
>>
>
>What about redesigning your URI space?
>
>You know, I'm not a friend of redirects as they where made to keep old
>URIs still working if you had to restructure your site. It seems to me
>that people think redirection is a tool/pattern for web development.
>
I agree with you, but the problem of old URIs will probably exist for
another year or so:-)
I think there are at least two solutions:
1) You can propagate the modifications of URIs through the net using a
P2P approach
or something similar. This would not only be good for old URIs, but also
for URIs where
content is changing all the time, such as for instance RSS. (For
instance Slashdot has the
policy that you are not "allowed" to request their RSS more often than
every 30 minutes,
else your IP will be blocked.)
2) Each URI has an owner. When the URI is old (expired), but is still
being requested, then the server should tell the owner about it
Both solutions could be part of a Content Management System/Framework.
But there is also another "misuse" of redirects:
Companies (for instance newspapers) sometimes want to announce a new
"product"
on the web, but the URI is too long for people remembering when reading
the adds,
but actually it would be appropriate context-wise. So the marketing
department thinks
of an "abbreviated" URI.
All the best
Michael
>
>
>Giacomo
>
>
>---------------------------------------------------------------------
>Please check that your question has not already been answered in the
>FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
>To unsubscribe, e-mail: <[EMAIL PROTECTED]>
>For additional commands, e-mail: <[EMAIL PROTECTED]>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
