1.1 --- a/docs/paths.html Sat Apr 09 23:50:49 2005 +0000
1.2 +++ b/docs/paths.html Sun Apr 10 21:11:25 2005 +0000
1.3 @@ -1,6 +1,6 @@
1.4 <?xml version="1.0" encoding="iso-8859-1"?>
1.5 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
1.6 - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
1.7 + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
1.8 <html xmlns="http://www.w3.org/1999/xhtml">
1.9 <head>
1.10 <title>URLs and Paths</title>
1.11 @@ -38,8 +38,7 @@
1.12 concentrate on the path because the address doesn't usually tell you anything
1.13 you don't already know. What you need to do is to interpret the path
1.14 specified in the request in order to work out which resource or service the
1.15 -request is destined for.<br />
1.16 -</p>
1.17 +request is destined for.</p>
1.18
1.19 <div class="WebStack">
1.20 <h3>WebStack API - Path Methods in Transaction Objects</h3>
1.21 @@ -49,14 +48,23 @@
1.22 <dl>
1.23 <dt><code>get_path</code></dt>
1.24 <dd>This gets the entire path of a resource including parameter
1.25 - information - see <a href="parameters.html">"Request Parameters and
1.26 - Uploads"</a>.</dd>
1.27 + information (as described in <a href="parameters.html">"Request
1.28 + Parameters and Uploads"</a>).</dd>
1.29 <dt><code>get_path_without_query</code></dt>
1.30 <dd>This gets the entire path of a resource but without any parameter
1.31 information.</dd>
1.32 </dl>
1.33 </div>
1.34
1.35 +<p>Sometimes, a "query string" will be provided as part of a URL; for
1.36 +example:</p>
1.37 +<pre>http://www.boddie.org.uk/application?param1=value1</pre>
1.38 +
1.39 +<p>The question mark character marks the beginning of the query string which
1.40 +contains encoded parameter information; such information and its inspection
1.41 +is discussed in <a href="parameters.html">"Request Parameters and
1.42 +Uploads"</a>.</p>
1.43 +
1.44 <h2>Paths To and Within an Application</h2>
1.45 One thing to be aware of in the code of an application is which part of a
1.46 path refers to the location of the application in a server environment and