| paulb@654 | 1 | <?xml version="1.0" encoding="iso-8859-1"?> |
| paulb@357 | 2 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
| paulb@327 | 3 | <html xmlns="http://www.w3.org/1999/xhtml"> |
| paulb@327 | 4 | <head> |
| paulb@327 | 5 | <title>Using the Path as an Opaque Reference into an Application</title> |
| paulb@328 | 6 | <link href="styles.css" rel="stylesheet" type="text/css" /> |
| paulb@327 | 7 | </head> |
| paulb@327 | 8 | <body> |
| paulb@327 | 9 | <h1>Using the Path as an Opaque Reference into an Application</h1> |
| paulb@327 | 10 | <p>Since many Web applications have complete control over how paths are |
| paulb@654 | 11 | interpreted, the form of the path doesn't necessarily have to follow any |
| paulb@654 | 12 | obvious structure as far as users of your application is concerned. Here's an |
| paulb@327 | 13 | example:</p> |
| paulb@327 | 14 | <pre>/000251923572ax-0015</pre> |
| paulb@654 | 15 | <p>Many people would argue that such obscure references, whilst perfectly |
| paulb@654 | 16 | acceptable to machines, would make any application counter-intuitive and very |
| paulb@654 | 17 | difficult to reference. However, application developers sometimes do not want people |
| paulb@654 | 18 | "bookmarking" resources or functions within an application, and so such concerns don't matter to them.</p> |
| paulb@327 | 19 | </body> |
| paulb@327 | 20 | </html> |
