cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d...@cocoon.apache.org
Subject [Cocoon Wiki] Updated: SimpleContentModel
Date Fri, 14 Jan 2005 21:07:14 GMT
   Date: 2005-01-14T13:07:14
   Editor: MarkLundquist
   Wiki: Cocoon Wiki
   Page: SimpleContentModel
   URL: http://wiki.apache.org/cocoon/SimpleContentModel

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -137,7 +137,7 @@
 
 == "Trailing slash" resources ==
 
-Sometimes you really need a resource to be served at a URI that ends with a slash, because
it determines whether a relative link in the page denotes a ''child''(if the current URL has
a trailing slash), or a ''sibling'' (current URL has no trailing slash) of the current page.
 If the URL of the current page doesn't end with a slash (e.g., {{{path/to/dogs}}}), then
we have an annoying situation if we want to include a link on that page to a child resource
(e.g., {{{path/to/dogs/Bowser}}}).  Our choices are:
+Sometimes you really need a resource to be served at a URI that ends with a slash, because
it determines whether a relative link in the page denotes a ''child'' (if the current URL
has a trailing slash), or a ''sibling'' (current URL has no trailing slash) of the current
page.  If the URL of the current page doesn't end with a slash (e.g., {{{path/to/dogs}}}),
then we have an annoying situation if we want to include a link on that page to a child resource
(e.g., {{{path/to/dogs/Bowser}}}).  Our choices are:
 
  * Use a rooted URI, e.g. {{{<a href="/path/to/dogs/Bowser">}}}
     This arguably sucks... we'd like to avoid being tightly-coupled to site structure here.

Mime
View raw message