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