1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/docs/path-design.html Tue Apr 26 18:33:06 2005 +0000
1.3 @@ -0,0 +1,42 @@
1.4 +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
1.5 +<html xmlns="http://www.w3.org/1999/xhtml">
1.6 +<head>
1.7 + <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type" />
1.8 + <title>Path Design and Interpretation</title>
1.9 + <meta name="generator"
1.10 + content="amaya 8.1a, see http://www.w3.org/Amaya/" />
1.11 + <link href="styles.css" rel="stylesheet" type="text/css" />
1.12 +</head>
1.13 +<body>
1.14 +<h1>Path Design and Interpretation</h1>
1.15 +<p>There are various differing approaches to the problem of
1.16 +interpreting
1.17 +paths to resources within Web applications, but these can mostly be
1.18 +divided
1.19 +into three categories:</p>
1.20 +<table align="center" border="1" cellpadding="5" cellspacing="0"
1.21 + width="80%">
1.22 + <tbody>
1.23 + <tr>
1.24 + <th>Approach</th>
1.25 + <th>Examples</th>
1.26 + </tr>
1.27 + <tr>
1.28 + <td><a href="paths-filesystem.html">Path as filesystem</a></td>
1.29 + <td>WebDAV interface to a repository</td>
1.30 + </tr>
1.31 + <tr>
1.32 + <td><a href="paths-services.html">Path as resource or service
1.33 +identifier</a></td>
1.34 + <td>A Web shop with very simple paths, eg. <code>/products</code>,
1.35 + <code>/checkout</code>, <code>/orders</code></td>
1.36 + </tr>
1.37 + <tr>
1.38 + <td><a href="paths-opaque.html">Path as opaque reference</a></td>
1.39 + <td>An e-mail reader where the messages already have strange and
1.40 +unreadable message identifiers</td>
1.41 + </tr>
1.42 + </tbody>
1.43 +</table>
1.44 +</body>
1.45 +</html>