# HG changeset patch # User paulb # Date 1114897688 0 # Node ID 4afabafdf5cace3f5f880c38a71a0138e451d536 # Parent a6cc8e5f642d002d32820375e224d1375123b2f6 [project @ 2005-04-30 21:48:08 by paulb] Added notes about EndOfResponse. diff -r a6cc8e5f642d -r 4afabafdf5ca docs/responses.html --- a/docs/responses.html Sat Apr 30 21:47:58 2005 +0000 +++ b/docs/responses.html Sat Apr 30 21:48:08 2005 +0000 @@ -29,8 +29,7 @@
Although it is possible to produce some output and then to let
+the respond
function complete normally, sometimes it
+is appropriate to terminate the response and to hand control straight
+back to the server environment; in other words, to decide that no more
+activity will be performed within the application and to send the
+response immediately. Whilst just using a return
+statement might be adequate in many applications...
# In the respond method...+
if some_condition:
[Produce a response.]
return
[Produce a different response.]
...sometimes a resource's respond
method is being
+called from another resource, and it may be the case that this other
+resource may produce additional output if control is returned to it.
To provide a definitive end of response signal, a special exception +is available:
+from WebStack.Generic import EndOfResponse+
[The usual declarations for the resource and the respond method...]
# In the respond method (possibly called by another resource)...
if some_condition:
[Produce a response.]
raise EndOfResponse
This exception, when raised, ensures that the response is sent
+exactly as the resource intended upon raising the exception. Note that
+although WebStack.Generic.EndOfResponse
is an exception,
+it will not cause an error condition or change the response code in any
+way.
Just as applications might need to integrate with other systems in order to fetch information or to perform operations on behalf of the