# HG changeset patch
# User paulb
# Date 1114383398 0
# Node ID 064f02540579a5fc8a33fee114ebb4b2f5a7ffe2
# Parent  bb9b193cc3bc38932a411396a2ef5a6ecb782a63
[project @ 2005-04-24 22:56:38 by paulb]
Improved the trailing commentary somewhat.

diff -r bb9b193cc3bc -r 064f02540579 docs/resource-creation.html
--- a/docs/resource-creation.html	Sun Apr 24 22:47:22 2005 +0000
+++ b/docs/resource-creation.html	Sun Apr 24 22:56:38 2005 +0000
@@ -11,7 +11,7 @@
 <h1>How Resources are Created
 </h1>
 <p>In the&nbsp;<code>MyApplication</code>
-<a href="resources.html">example</a>,
+<a href="resources.html">example</a> (and in many applications),
 the only
 thing we need to
 consider is
@@ -70,13 +70,22 @@
     </tr>
   </tbody>
 </table>
+<h2>The Role of the Adapter</h2>
+<p>So it is the responsibility of the adapter to create at least one
+resource object so that the application code may be executed when a
+request is received from a user. This is described in the <a
+ href="deploying.html">deployment documentation</a>.</p>
+<h2>Creating Many Resources</h2>
 <p>In more
 complicated applications, there may
 be a
-need to create our own resource objects explicitly, but this is not
-particularly interesting to think about at this point - see <a
- href="paths-filesystem.html">"Treating the Path Like
+need to create a number of&nbsp;resource objects and possibly to do so
+dynamically within an application itself, but this is not usually
+interesting or relevant to think about when writing your first
+application - see <a href="paths-filesystem.html">"Treating the Path
+Like
 a Filesystem"</a> for a
-discussion of multiple resource objects.</p>
+discussion of creating new resource objects both in the adapter code
+and dynamically within applications.</p>
 </body>
 </html>