WebStack

docs/paths-opaque.html

401:ca2a40e20036
2005-07-16 paulb [project @ 2005-07-16 20:32:56 by paulb] Enhanced the PYTHONPATH handling to respect the existing definition.
     1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">     2 <html xmlns="http://www.w3.org/1999/xhtml">     3 <head>     4   <title>Using the Path as an Opaque Reference into an Application</title>     5   <meta name="generator"     6  content="amaya 8.1a, see http://www.w3.org/Amaya/" />     7   <link href="styles.css" rel="stylesheet" type="text/css" />     8 </head>     9 <body>    10 <h1>Using the Path as an Opaque Reference into an Application</h1>    11 <p>Since many Web applications have complete control over how paths are    12 interpreted, the form of the path doesn't necessarily have to follow    13 any    14 obvious structure as far as users of your application is concerned.    15 Here's an    16 example:</p>    17 <pre>/000251923572ax-0015</pre>    18 <p>Many people would argue that such obscure references, whilst    19 perfectly    20 acceptable to machines, would make any application counter-intuitive    21 and very    22 difficult to reference. However,&nbsp;application developers sometimes    23 do not want people    24 "bookmarking" resources or functions within an application, and so such    25 concerns don't matter to them.</p>    26 </body>    27 </html>