<?xml version="1.0"?>
<rss version="2.0">
  <channel><title>Caudium 1.5: memory leaks fixed</title><link>http://bertrand.gotpike.org//space/start/2006-02-03/1</link><description>There have been quite some interresting and construtive traffic recently on the caudium-devel mailing list:&#xD;
&lt;ul class="minus"&gt;
&lt;li&gt;January: &lt;span class="nobr"&gt;&lt;img height="9" width="8" src="/static/images/Icon-Extlink.png" alt="&amp;#91;external]"/&gt;&lt;a href="http://lists.oav.net/wws/arc/caudium-devel/2006-01/"&gt;http://lists.oav.net/wws/arc/caudium-devel/2006-01/&lt;/a&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;February: &lt;span class="nobr"&gt;&lt;img height="9" width="8" src="/static/images/Icon-Extlink.png" alt="&amp;#91;external]"/&gt;&lt;a href="http://lists.oav.net/wws/arc/caudium-devel/2006-02/"&gt;http://lists.oav.net/wws/arc/caudium-devel/2006-02/&lt;/a&gt;&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;This has lead to a nice cleanup of Caudium parts written in C that were leaking memory.&lt;p class="paragraph"/&gt;
We're waiting to see the results on some servers running on Caudium 1.5.1-CVS, but i'm quite excited to backport these changes on Caudium 1.4 and upgrade my production servers.</description><generator>Fins 0.9.7</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs></channel>
</rss>
