Relative URI Problem

<h1>Relative URI Problem</h1>

<p>TIR navigation depends on using relative URIs for local pages so that browsers can follow links regardless of whether the pages are hosted on a web server or on the local file system.</p>

<p>However, the path Net Front (and likely most other browsers) uses to resolve a relative URI for a given directory may <em>vary</em> if the directory can be accessed both by it's natural path and by alternative paths created with links, which TIR uses to create thematic connections between directories.</p>

<p>This renders relative URIs void when a page is accessed through a link.</p>

<h2>Possible Solutions</h2>

<ol>
<li>Abandon TIR and use Blosxom,</li>

<li>Remove directory link support.</li>

<li>Use links in each directory for shared resources (stylesheets, "tool" and "feature" pages (.menu1, .menu2 links) and use local URIs for those links instead of relative URIs.</li>

<li>Replace link files with another mechanism for representing topical relationships, such as supporting an optional .links (or .exits to keep with the MUD theme) that contains a list of relative URIs to related directories.</li>
</ol>

<p>Number 4. looks like the most efficient way to preserve intended functionality.</p>