shannon     2002/07/10 11:50:11

  Modified:    src/documentation/xdocs/faq faq-sitemap.xml
  Log:
  Added new faq about differences between pipelines
  thanks to Konstantin's post on cocoon-dev.
  
  Revision  Changes    Path
  1.6       +32 -2     xml-cocoon2/src/documentation/xdocs/faq/faq-sitemap.xml
  
  Index: faq-sitemap.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/faq/faq-sitemap.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- faq-sitemap.xml   1 Jul 2002 19:55:01 -0000       1.5
  +++ faq-sitemap.xml   10 Jul 2002 18:50:11 -0000      1.6
  @@ -232,6 +232,36 @@
     </answer>
   </faq>
   
  -
  -
  +<faq>
  +  <question>
  +What's the difference between having two pipelines with one matcher 
  +each, and one pipeline with two matchers?
  +  </question>
  +  <answer>
  +   <p>
  +If there is no other difference in pipeline declarations, then none, really. Note 
that pipelines can differ by:
  +  </p>
  +<ul>
  +     <li>
  +visibility: internal-only="true" (not accessible for external requests) or not.
  +   </li>
  +   <li>
  +error handling: using different &lt;handle-errors&gt;s.
  +   </li>
  +   <li>
  +cachability (since 2.1): some requests can use cached responses
  +from caching pipeline. Others, which should not be cached, can be
  +handled by the non-caching pipeline implementation.
  +  </li>
  +  <li>
  +logical grouping: logically-related components can be grouped into
  +separate pipelines to improve readability and ease administrative concerns.
  +  </li>
  +  <li>
  +ids: used to identify pipeline and other elements. See the "sitebuilder" sitemap 
editor
  +in scratchpad samples for an example.
  +  </li>
  +</ul>
  + </answer>
  + </faq>
   </faqs>
  
  
  

----------------------------------------------------------------------
In case of troubles, e-mail:     [EMAIL PROTECTED]
To unsubscribe, e-mail:          [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to