vmassol     01/09/21 02:25:54

  Modified:    docs/framework/xdocs todo.xml
  Log:
  new todo ...
  
  Revision  Changes    Path
  1.58      +12 -0     jakarta-cactus/docs/framework/xdocs/todo.xml
  
  Index: todo.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/docs/framework/xdocs/todo.xml,v
  retrieving revision 1.57
  retrieving revision 1.58
  diff -u -r1.57 -r1.58
  --- todo.xml  2001/09/20 19:31:35     1.57
  +++ todo.xml  2001/09/21 09:25:54     1.58
  @@ -87,6 +87,18 @@
   
       <category title="Design/Code">
         <action>
  +        Add methods that are called before and after each test, but on the
  +        client side (i.e. before the <code>beginXXX()</code> and 
  +        <code>endXXX()</code> methods). They
  +        would act the same way as <code>setUp()</code> and 
  +        <code>tearDown()</code> but on the client side. They could be
  +        named <code>init()</code> and <code>destroy()</code>, or maybe we
  +        should rather rename the existing <code>setUp()</code> and
  +        <code>tearDown()</code> and have something consistent like :
  +        <code>setUpClient()</code>, <code>setUpServer()</code>,
  +        <code>tearDownClient()</code> and <code>tearDownServer()</code> ?
  +      </action>
  +      <action>
           Provide support for generating Session cookies and URL Sessions
           (URL rewriting). A description of the mechanism has been
           posted in thread "How does cactus simulate a session" on the
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to