Bob Harner wrote: [...]
Let me see if I'm following you: the only reason for rewriting links at display time (rather than when the CMS document is create/modified) is so that we can remove any links that point to other CMS documents that have been deleted or moved, right?
Yes, unless I'm missing something.
This seems like an I/O and CPU hog for pages with lots of links, and the benefit seems minimal. Personally, I might rather have a broken link than a removed link anyway :-)
OK, than it should be possible to switch this functionality on/off.
because at least I can use external tools to detect broken links, but not if we remove them. (I know that in 1.4 such links to missing documents are displayed specially, but not so in the live area.) The reason I'm interested in this point is that I'd like to see LinkRewritingTransformer do a much more thorough job, as I repeated in another recent thread, but I wouldn't want it to slow down the display of pages. Having a link management capability would be the proper solution, of course (so that when you delete or move a document then you could just "look up" the list of documents that pointed to it),
+1
but that would be very hard to do without a relational database.
Using JCR and UUIDs would certainly make it easier. Let's discuss our ideas and requirements in the LinkRewritingTransformer thread and see what we'll come up with. -- Andreas -- Andreas Hartmann Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://lenya.apache.org [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
