svn commit: r389446 - /cocoon/branches/BRANCH_2_1_X/status.xml

[mp...@apache.org]

Author: mpfingsthorn
Date: Tue Mar 28 01:02:03 2006
New Revision: 389446

URL: http://svn.apache.org/viewcvs?rev=389446&view=rev
Log:
added latest changes by myself

Modified:
    cocoon/branches/BRANCH_2_1_X/status.xml

Modified: cocoon/branches/BRANCH_2_1_X/status.xml
URL: http://svn.apache.org/viewcvs/cocoon/branches/BRANCH_2_1_X/status.xml?rev=389446&r1=389445&r2=389446&view=diff
==============================================================================
--- cocoon/branches/BRANCH_2_1_X/status.xml (original)
+++ cocoon/branches/BRANCH_2_1_X/status.xml Tue Mar 28 01:02:03 2006
@@ -99,6 +99,7 @@
   <person name="Steven Noels" email="stevenn@apache.org" id="SN"/>
   <person name="Christopher Oliver" email="coliver@apache.org" id="CO"/>
   <person name="Giacomo Pati" email="giacomo@apache.org" id="GP"/>
+  <person name="Max Pfingsthorn" email="mpfingsthorn@apache.org" id="MPF"/>
   <person name="Konstantin Piroumian" email="kpiroumian@apache.org" id="KP"/>
   <person name="Marc Portier" email="mpo@apache.org" id="MPO"/>
   <person name="Ovidiu Predescu" email="ovidiu@apache.org" id="OP"/>
@@ -469,6 +470,21 @@
     <action dev="AN" type="fix" fixes-bug="COCOON-1691" due-to="Feliciano Borrego" due-to-email="felibv@gmail.com">
       Database block: Renaming AttributeImpl xspAttr to _xspAttr was not applied to ESQL logicsheet.
       That caused compliation errors in all XSPs using it.
+    </action>
+    <action dev="MPF" type="add">
+      Core: Error handling fixed in map:aggregate (ContentAggregator). Now, no content is prepended to the
+      result of any error handling pipeline.
+    </action>
+    <action dev="MPF" type="add">
+      Core: Caching pipelines (CachingProcessingPipeline, ExpiresCachingProcessingPipeline, ...) will now check
+      if the content they are trying to generate is already being generated by another caching pipeline.
+      If so, they will wait for that content to appear in the Cache and use that content instead of
+      re-generating it and possibly causing high load on the server.
+    </action>
+    <action dev="MPF" type="add">
+      Core: ExpiresCachingProcessingPipeline will not set up a pipeline anymore when a cached
+      version of it is available. Any cached response will now serve quickly, no matter how
+      complex the actual pipeline is.
     </action>
   </release>
   <release version="2.1.8" date="November 18 2005">