1.1 --- a/docs/responses.html Fri Oct 14 13:56:48 2005 +0000
1.2 +++ b/docs/responses.html Wed Oct 19 17:19:49 2005 +0000
1.3 @@ -1,11 +1,9 @@
1.4 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
1.5 -<html xmlns="http://www.w3.org/1999/xhtml">
1.6 -<head>
1.7 - <title>Responses and Presentation</title>
1.8 - <meta name="generator"
1.9 - content="amaya 8.1a, see http://www.w3.org/Amaya/" />
1.10 - <link href="styles.css" rel="stylesheet" type="text/css" />
1.11 -</head>
1.12 +<html xmlns="http://www.w3.org/1999/xhtml"><head>
1.13 +
1.14 + <title>Responses and Presentation</title><meta name="generator" content="amaya 8.1a, see http://www.w3.org/Amaya/" />
1.15 + <link href="styles.css" rel="stylesheet" type="text/css" /></head>
1.16 +
1.17 <body>
1.18 <h1>Responses and Presentation</h1>
1.19 <p>After performing some kind of
1.20 @@ -29,7 +27,7 @@
1.21 <li>Setting a response code to
1.22 signal whether the application performed the requested operation
1.23 successfully.</li>
1.24 - <li>Setting a content type and a <a>character encoding</a>.</li>
1.25 + <li>Setting a content type and a <a>character encoding</a>.</li><li>Possibly setting some response headers.</li>
1.26 <li>Producing content and
1.27 sending it to the user.</li>
1.28 </ol>
1.29 @@ -61,9 +59,13 @@
1.30 relevant) of the data sent to the user. The media type describes the
1.31 format of the data (eg. <code>text/html</code>
1.32 - a Web page), whereas the character encoding describes how any
1.33 -character information on the page is encoded - see <a
1.34 - href="encodings.html">"Character Encodings"</a>
1.35 -for more information.</dd>
1.36 +character information on the page is encoded - see <a href="encodings.html">"Character Encodings"</a>
1.37 +for more information.</dd><dt><code>set_header_value</code></dt><dd>This
1.38 +accepts a header name and a corresponding value. Response headers
1.39 +convey information to the user (and their software) which is comparable
1.40 +to that found in <a href="headers.html">request headers</a> sent in to
1.41 +the Web application; for example, the content type information is
1.42 +transmitted using response headers (using the <code>Content-Type</code> header name), although the above <code>set_content_type</code> method is a more convenient means of preparing such information.</dd>
1.43 <dt><code>get_response_stream</code></dt>
1.44 <dd>This returns the output
1.45 stream through which data may be sent to the user.</dd>
1.46 @@ -101,5 +103,4 @@
1.47 displayed as a Web page (amongst other things).</p>
1.48 <p>See <a href="integrating.html">"Integration with Other Systems"</a>
1.49 for more information on the principles of using such external libraries.</p>
1.50 -</body>
1.51 -</html>
1.52 +</body></html>
1.53 \ No newline at end of file