WebStack

docs/paths-opaque.html

733:26865b172666
2007-11-12 paulb [project @ 2007-11-12 00:51:34 by paulb] Added a StringResource class for simple static resources. Introduced base classes for common authentication activities. Merged "app", "path" and "qs" fields into a single "app" field for login and redirection. Added support for OpenID authentication.
     1 <?xml version="1.0" encoding="iso-8859-1"?>     2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">     3 <html xmlns="http://www.w3.org/1999/xhtml">     4 <head>     5   <title>Using the Path as an Opaque Reference into an Application</title>     6   <link href="styles.css" rel="stylesheet" type="text/css" />     7 </head>     8 <body>     9 <h1>Using the Path as an Opaque Reference into an Application</h1>    10 <p>Since many Web applications have complete control over how paths are    11 interpreted, the form of the path doesn't necessarily have to follow any    12 obvious structure as far as users of your application is concerned. Here's an    13 example:</p>    14 <pre>/000251923572ax-0015</pre>    15 <p>Many people would argue that such obscure references, whilst perfectly    16 acceptable to machines, would make any application counter-intuitive and very    17 difficult to reference. However, application developers sometimes do not want people    18 "bookmarking" resources or functions within an application, and so such concerns don't matter to them.</p>    19 </body>    20 </html>