1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/docs/paths-opaque.html Fri Apr 08 22:33:56 2005 +0000
1.3 @@ -0,0 +1,28 @@
1.4 +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
1.5 +<html xmlns="http://www.w3.org/1999/xhtml">
1.6 +<head>
1.7 + <title>Using the Path as an Opaque Reference into an Application</title>
1.8 + <meta name="generator"
1.9 + content="amaya 8.1a, see http://www.w3.org/Amaya/">
1.10 + <link xmlns:xlink="http://www.w3.org/1999/xlink" href="styles.css"
1.11 + rel="stylesheet" type="text/css">
1.12 +</head>
1.13 +<body>
1.14 +<h1>Using the Path as an Opaque Reference into an Application</h1>
1.15 +<p>Since many Web applications have complete control over how paths are
1.16 +interpreted, the form of the path doesn't necessarily have to follow
1.17 +any
1.18 +obvious structure as far as users of your application is concerned.
1.19 +Here's an
1.20 +example:</p>
1.21 +<pre>/000251923572ax-0015</pre>
1.22 +<p>However, many would argue that such obscure references, whilst
1.23 +perfectly
1.24 +acceptable to machines, would make any application counter-intuitive
1.25 +and very
1.26 +difficult to reference. Sometimes, application developers do not want
1.27 +people
1.28 +"bookmarking" resources or functions within an application, and so such
1.29 +concerns don't matter to them.</p>
1.30 +</body>
1.31 +</html>