| paulb@328 | 1 | <?xml version="1.0" encoding="iso-8859-1"?> |
| paulb@328 | 2 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" |
| paulb@328 | 3 | "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
| paulb@327 | 4 | <html xmlns="http://www.w3.org/1999/xhtml"> |
| paulb@327 | 5 | <head> |
| paulb@327 | 6 | <title>Treating the Path Mostly Like a Filesystem</title> |
| paulb@328 | 7 | <meta name="generator" content="amaya 8.1a, see http://www.w3.org/Amaya/" /> |
| paulb@328 | 8 | <link href="styles.css" rel="stylesheet" type="text/css" /> |
| paulb@327 | 9 | </head> |
| paulb@328 | 10 | |
| paulb@327 | 11 | <body> |
| paulb@327 | 12 | <h1>Treating the Path Mostly Like a Filesystem</h1> |
| paulb@328 | 13 | |
| paulb@327 | 14 | <p>...but really using it to broadly identify different resources or |
| paulb@327 | 15 | services. In this approach, we take a path like this...</p> |
| paulb@327 | 16 | <pre>/tools/viewer</pre> |
| paulb@328 | 17 | |
| paulb@327 | 18 | <p>...and interpret it as being a request for a certain function of the |
| paulb@328 | 19 | application. Often, this approach is used because it matches some aspect of |
| paulb@327 | 20 | how the application is actually organised. Consider this example:</p> |
| paulb@327 | 21 | <pre>/cgi-bin/script.pl</pre> |
| paulb@328 | 22 | |
| paulb@327 | 23 | <p>This kind of thing generally appears in URLs because of the way the |
| paulb@328 | 24 | application concerned has been deployed - CGI programs live in a particular |
| paulb@327 | 25 | place and are accessed using a special path "prefix".</p> |
| paulb@327 | 26 | </body> |
| paulb@327 | 27 | </html> |
