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