1.1 --- a/docs/paths.html Fri Apr 08 22:33:56 2005 +0000
1.2 +++ b/docs/paths.html Fri Apr 08 23:09:33 2005 +0000
1.3 @@ -1,10 +1,11 @@
1.4 -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
1.5 -<html>
1.6 +<?xml version="1.0" encoding="iso-8859-1"?>
1.7 +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
1.8 + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
1.9 +<html xmlns="http://www.w3.org/1999/xhtml">
1.10 <head>
1.11 - <meta http-equiv="Content-Type" content="text/html">
1.12 <title>URLs and Paths</title>
1.13 - <meta name="generator" content="amaya 8.1a, see http://www.w3.org/Amaya/">
1.14 - <link href="styles.css" rel="stylesheet" type="text/css">
1.15 + <meta name="generator" content="amaya 8.1a, see http://www.w3.org/Amaya/" />
1.16 + <link href="styles.css" rel="stylesheet" type="text/css" />
1.17 </head>
1.18
1.19 <body>
1.20 @@ -37,7 +38,7 @@
1.21 concentrate on the path because the address doesn't usually tell you anything
1.22 you don't already know. What you need to do is to interpret the path
1.23 specified in the request in order to work out which resource or service the
1.24 -request is destined for.<br>
1.25 +request is destined for.<br />
1.26 </p>
1.27
1.28 <div class="WebStack">
1.29 @@ -60,7 +61,7 @@
1.30 One thing to be aware of in the code of an application is which part of a
1.31 path refers to the location of the application in a server environment and
1.32 which refers to some resource within the application itself. Consider this
1.33 -path:<br>
1.34 +path:<br />
1.35
1.36 <pre>/folder/application/resource</pre>
1.37 Let us say that the application was deployed in a Zope server instance inside
1.38 @@ -86,8 +87,7 @@
1.39 </dl>
1.40 </div>
1.41
1.42 -<h2>Approaches to Path Interpretation<br>
1.43 -</h2>
1.44 +<h2>Approaches to Path Interpretation</h2>
1.45
1.46 <p>There are various differing approaches to the problem of interpreting
1.47 paths to resources within Web applications, but these can mostly be divided
1.48 @@ -116,5 +116,53 @@
1.49 </tr>
1.50 </tbody>
1.51 </table>
1.52 +
1.53 +<h2>Path Info Support in Server Environments</h2>
1.54 +
1.55 +<p>The following table summarises the support for paths within applications
1.56 +amongst the supported server environments or frameworks within WebStack:</p>
1.57 +
1.58 +<table border="1" cellspacing="0" cellpadding="5">
1.59 + <tbody>
1.60 + <tr>
1.61 + <th>Framework</th>
1.62 + <th>Behaviour/Level of Support</th>
1.63 + </tr>
1.64 + <tr>
1.65 + <td>BaseHTTPRequestHandler</td>
1.66 + <td>Same as path (correct)</td>
1.67 + </tr>
1.68 + <tr>
1.69 + <td>CGI</td>
1.70 + <td>Path beyond resource (correct)</td>
1.71 + </tr>
1.72 + <tr>
1.73 + <td>Java Servlet API</td>
1.74 + <td>Path beyond context (correct)</td>
1.75 + </tr>
1.76 + <tr>
1.77 + <td>mod_python</td>
1.78 + <td>Path beyond resource (correct)</td>
1.79 + </tr>
1.80 + <tr>
1.81 + <td>Twisted</td>
1.82 + <td>Same as path (correct)</td>
1.83 + </tr>
1.84 + <tr>
1.85 + <td>Webware</td>
1.86 + <td><= 0.8.1: Not supported (needs <code>ExtraPathInfo</code>
1.87 + support)<br />
1.88 + > 0.8.1: Path beyond context (correct)</td>
1.89 + </tr>
1.90 + <tr>
1.91 + <td>WSGI</td>
1.92 + <td>Path beyond resource (correct)</td>
1.93 + </tr>
1.94 + <tr>
1.95 + <td>Zope</td>
1.96 + <td>Path beyond resource (correct)</td>
1.97 + </tr>
1.98 + </tbody>
1.99 +</table>
1.100 </body>
1.101 </html>