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 <link href="styles.css" rel="stylesheet" type="text/css" /> 8 </head> 9 10 <body> 11 <h1>Treating the Path Mostly Like a Filesystem</h1> 12 13 <p>...but really using it to broadly identify different resources or 14 services. In this approach, we take a path like this...</p> 15 <pre>/tools/viewer</pre> 16 17 <p>...and interpret it as being a request for a certain function of the 18 application. Often, this approach is used because it matches some aspect of 19 how the application is actually organised. Consider this example:</p> 20 <pre>/cgi-bin/script.pl</pre> 21 22 <p>This kind of thing generally appears in URLs because of the way the 23 application concerned has been deployed - CGI programs live in a particular 24 place and are accessed using a special path "prefix".</p> 25 </body> 26 </html>