cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From craft...@apache.org
Subject cvs commit: xml-cocoon2/src/webapp/samples/flow/docs how-does-it-work.xml continuations.xml
Date Wed, 04 Dec 2002 13:58:49 GMT
crafterm    2002/12/04 05:58:48

  Modified:    src/webapp/samples/flow/docs how-does-it-work.xml
                        continuations.xml
  Log:
  Updated flow documentation to reflect sendPage* name changes.
  
  Revision  Changes    Path
  1.3       +1 -1      xml-cocoon2/src/webapp/samples/flow/docs/how-does-it-work.xml
  
  Index: how-does-it-work.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/src/webapp/samples/flow/docs/how-does-it-work.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- how-does-it-work.xml	31 Oct 2002 11:59:05 -0000	1.2
  +++ how-does-it-work.xml	4 Dec 2002 13:58:48 -0000	1.3
  @@ -12,7 +12,7 @@
     <body>
       <s1 title="Cocoon and continuations">
   	<p>With continuations in the language, you can essentially
  -	store the continuation of <code>sendPage</code> (think of all
  +	store the continuation of <code>sendPageAndWait</code> (think of all
   	the stack trace, and the program counter), put it in a global
   	hash table associated with an id. The id is then encoded in
   	the <code>response.xml</code> page as an URL. When the user
  
  
  
  1.3       +6 -6      xml-cocoon2/src/webapp/samples/flow/docs/continuations.xml
  
  Index: continuations.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/src/webapp/samples/flow/docs/continuations.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- continuations.xml	31 Oct 2002 11:59:05 -0000	1.2
  +++ continuations.xml	4 Dec 2002 13:58:48 -0000	1.3
  @@ -34,13 +34,13 @@
   {
     var a, b, operator;
   
  -  sendPage("getA.html");
  +  sendPageAndWait("getA.html");
     a = request.getParameter("a");
   
  -  sendPage("getB.html");
  +  sendPageAndWait("getB.html");
     b = request.getParameter("b");
   
  -  sendPage("getOperator.html");
  +  sendPageAndWait("getOperator.html");
     operator = request.getParameter("op");
   
     try {
  @@ -63,14 +63,14 @@
   
         <p>In this example, the <code>calculator</code> function is
         called to start the calculator application. We'd like the
  -      <code>sendPage</code> function to be a special function, that
  +      <code>sendPageAndWait</code> function to be a special function, that
         takes as arguments an HTML file to be sent as response, and some
         optional data that needs to be placed dynamically in it. We
  -      would like <code>sendPage</code> to send the response page and
  +      would like <code>sendPageAndWait</code> to send the response page and
         then block the executing thread, until the user clicks on a link
         in the response page, which sends a request back to the
         server. This request resumes the processing at the point it was
  -      left, right after the call to <code>sendPage</code>.</p>
  +      left, right after the call to <code>sendPageAndWait</code>.</p>
   
         <p>This approach looks very powerful, since the flow of pages
         within the application can be described as a normal
  
  
  

----------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          cocoon-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-cvs-help@xml.apache.org


Mime
View raw message