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 <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type" /> 5 <title>Path Design and Interpretation</title> 6 <meta name="generator" 7 content="amaya 8.1a, see http://www.w3.org/Amaya/" /> 8 <link href="styles.css" rel="stylesheet" type="text/css" /> 9 </head> 10 <body> 11 <h1>Path Design and Interpretation</h1> 12 <p>There are various differing approaches to the problem of 13 interpreting 14 paths to resources within Web applications, but these can mostly be 15 divided 16 into three categories:</p> 17 <table align="center" border="1" cellpadding="5" cellspacing="0" 18 width="80%"> 19 <tbody> 20 <tr> 21 <th>Approach</th> 22 <th>Examples</th> 23 </tr> 24 <tr> 25 <td><a href="paths-filesystem.html">Path as filesystem</a></td> 26 <td>WebDAV interface to a repository</td> 27 </tr> 28 <tr> 29 <td><a href="paths-services.html">Path as resource or service 30 identifier</a></td> 31 <td>A Web shop with very simple paths, eg. <code>/products</code>, 32 <code>/checkout</code>, <code>/orders</code></td> 33 </tr> 34 <tr> 35 <td><a href="paths-opaque.html">Path as opaque reference</a></td> 36 <td>An e-mail reader where the messages already have strange and 37 unreadable message identifiers</td> 38 </tr> 39 </tbody> 40 </table> 41 </body> 42 </html>
