1.1 --- a/docs/paths-services.html Fri Apr 08 22:33:56 2005 +0000
1.2 +++ b/docs/paths-services.html Fri Apr 08 23:09:33 2005 +0000
1.3 @@ -1,25 +1,27 @@
1.4 -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
1.5 +<?xml version="1.0" encoding="iso-8859-1"?>
1.6 +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
1.7 + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
1.8 <html xmlns="http://www.w3.org/1999/xhtml">
1.9 <head>
1.10 <title>Treating the Path Mostly Like a Filesystem</title>
1.11 - <meta name="generator"
1.12 - content="amaya 8.1a, see http://www.w3.org/Amaya/">
1.13 - <link xmlns:xlink="http://www.w3.org/1999/xlink" href="styles.css"
1.14 - 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 <h1>Treating the Path Mostly Like a Filesystem</h1>
1.21 +
1.22 <p>...but really using it to broadly identify different resources or
1.23 services. In this approach, we take a path like this...</p>
1.24 <pre>/tools/viewer</pre>
1.25 +
1.26 <p>...and interpret it as being a request for a certain function of the
1.27 -application. Often, this approach is used because it matches some
1.28 -aspect of
1.29 +application. Often, this approach is used because it matches some aspect of
1.30 how the application is actually organised. Consider this example:</p>
1.31 <pre>/cgi-bin/script.pl</pre>
1.32 +
1.33 <p>This kind of thing generally appears in URLs because of the way the
1.34 -application concerned has been deployed - CGI programs live in a
1.35 -particular
1.36 +application concerned has been deployed - CGI programs live in a particular
1.37 place and are accessed using a special path "prefix".</p>
1.38 </body>
1.39 </html>