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