Index: packages.lisp
===================================================================
--- packages.lisp	(revision 4474)
+++ packages.lisp	(working copy)
@@ -168,6 +168,7 @@
            "DELETE-AUX-REQUEST-VALUE"
            "DELETE-SESSION-VALUE"
            "DISPATCH-EASY-HANDLERS"
+	   "DISPATCH-REQUEST"
            "ESCAPE-FOR-HTML"
            "EXECUTE-ACCEPTOR"
            "GET-PARAMETER"
Index: request.lisp
===================================================================
--- request.lisp	(revision 4474)
+++ request.lisp	(working copy)
@@ -95,21 +95,22 @@
 can subclass REQUEST in order to implement your own behaviour.  See
 the REQUEST-CLASS slot of the ACCEPTOR class."))
 
+(defgeneric dispatch-request (request)
+  (:documentation "This function is called by PROCESS-REQUEST. It
+selects and calls a handler to process the request.
+
+This might be a good place to introduce around methods which bind
+special variables or do other interesting things that are relevant to
+the particular request. Note that DISPATCH-REQUEST is called once per
+connection and loops in case of a persistent connection, while
+PROCESS-REQUEST is called anew for each request."))
+  
 (defgeneric process-request (request)
   (:documentation "This function is called by PROCESS-CONNECTION after
-the incoming headers have been read.  It selects and calls a handler
-and sends the output of this handler to the client using START-OUTPUT.
-It also sets up simple error handling for the request handler.  Note
-that PROCESS-CONNECTION is called once per connection and loops in
-case of a persistent connection while PROCESS-REQUEST is called anew
-for each request.
+the incoming headers have been read.  It calls DISPATCH-REQUEST and
+sends its output to the client.  It also sets up simple error handling
+for the request handler."))
 
-Like PROCESS-CONNECTION, this might be a good place to introduce
-around methods which bind special variables or do other interesting
-things.
-
-The return value of this function is ignored."))
-
 (defun convert-hack (string external-format)
   "The rfc2388 package is buggy in that it operates on a character
 stream and thus only accepts encodings which are 8 bit transparent.
@@ -210,6 +211,12 @@
         ;; we assume it's not our fault...
         (setf (return-code*) +http-bad-request+)))))
 
+(defmethod dispatch-request (request)
+  "Standard implementation of dispatching a request to the appropriate
+handler."
+  (funcall (acceptor-request-dispatcher *acceptor*)
+	   request))
+
 (defmethod process-request (request)
   "Standard implementation for processing a request.  You should not
 change or replace this functionality unless you know what you're
@@ -227,7 +234,7 @@
                      ;; skip dispatch if bad request
                      (when (eql (return-code *reply*) +http-ok+)
                        ;; now do the work
-                       (funcall (acceptor-request-dispatcher *acceptor*) *request*)))))
+                       (dispatch-request request)))))
               (when error
                 (setf (return-code *reply*)
                       +http-internal-server-error+))
Index: doc/index.xml
===================================================================
--- doc/index.xml	(revision 4474)
+++ doc/index.xml	(working copy)
@@ -1594,17 +1594,33 @@
   </clix:returns>
     <clix:description>
 This function is called by <clix:ref>PROCESS-CONNECTION</clix:ref>
-after the incoming headers have been read.  It selects and calls a
-<a href="#handlers">handler</a> and sends the output of this handler
-to the client.  It also sets up simple error handling for the request
-handler.  Note that <clix:ref>PROCESS-CONNECTION</clix:ref> is called
-once per connection and loops in case of a persistent connection
+after the incoming headers have been read.  It
+calls <clix:ref>DISPATCH-REQUEST</clix:ref> and sends its output to
+the client.  It also sets up simple error handling for the request
+handler.
+<p>
+The return value of this function is ignored.
+</p>
+    </clix:description>
+  </clix:function>
+
+  <clix:function generic='true' name='dispatch-request'>
+  <clix:lambda-list>request
+  </clix:lambda-list>
+  <clix:returns>nil
+  </clix:returns>
+    <clix:description>
+This function is called by <clix:ref>PROCESS-REQUEST</clix:ref>. It
+selects and calls a
+<a href="#handlers">handler</a> to process the request. 
+<p>
+This might be a good place to introduce around methods which bind
+special variables or do other interesting things that are relevant to
+the particular request. Note
+that <clix:ref>DISPATCH-REQUEST</clix:ref> is called once per
+connection and loops in case of a persistent connection,
 while <clix:ref>PROCESS-REQUEST</clix:ref> is called anew for each
 request.
-<p>
-Like <clix:ref>PROCESS-CONNECTION</clix:ref>, this might be a good
-place to introduce around methods which bind special variables or do
-other interesting things.
 </p>
 <p>
 The return value of this function is ignored.
