<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to news</title><link href="https://sourceforge.net/p/openlc/news/" rel="alternate"/><link href="https://sourceforge.net/p/openlc/news/feed.atom" rel="self"/><id>https://sourceforge.net/p/openlc/news/</id><updated>2002-06-24T12:13:04Z</updated><subtitle>Recent posts to news</subtitle><entry><title>OpenLC enters Beta (0.6 is out)!</title><link href="https://sourceforge.net/p/openlc/news/2002/06/openlc-enters-beta-06-is-out/" rel="alternate"/><published>2002-06-24T12:13:04Z</published><updated>2002-06-24T12:13:04Z</updated><author><name>Francesc Altet</name><uri>https://sourceforge.net/u/falted/</uri></author><id>https://sourceforge.net6b7ead24ae644abd53f7ef7fdaf82bb7f8227243</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I've released the first beta of OpenLC. &lt;br /&gt;
It's version 0.6. It has several&lt;br /&gt;
improvements over version 0.5: run database&lt;br /&gt;
redesigned (now using a mix of XML, NetCDF&lt;br /&gt;
and HDF5), speed increase, IMAP4 support,&lt;br /&gt;
better and more configurable statistics,&lt;br /&gt;
and last but not least much improved&lt;br /&gt;
documentation!.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>OpenLC 0.5 is out</title><link href="https://sourceforge.net/p/openlc/news/2001/12/openlc-05-is-out/" rel="alternate"/><published>2001-12-20T19:09:21Z</published><updated>2001-12-20T19:09:21Z</updated><author><name>Francesc Altet</name><uri>https://sourceforge.net/u/falted/</uri></author><id>https://sourceforge.net05f451be7f1f7c313fd72a5bb96b17a2edbf95af</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Two moths after first public release (v0.3) &lt;br /&gt;
arrives the 0.5. Version 0.4 was internal and will&lt;br /&gt;
never be released. v0.4 wasn't in time for many&lt;br /&gt;
reasons, but the most important one was a memory&lt;br /&gt;
leak detected on the ZODB database OpenLC used to&lt;br /&gt;
keep all the data. After two weeks browsing at the&lt;br /&gt;
ZODB lists (where more people reported similar&lt;br /&gt;
problems) and doing some debugging, I've decided&lt;br /&gt;
to use the very well tested Berkeley DB (from&lt;br /&gt;
SleepyCat) instead. Now, OpenLC runs much better,&lt;br /&gt;
with no perceptible memory leaks (at least, on my&lt;br /&gt;
rather small tests!). The drawback is that I've&lt;br /&gt;
added 2 new packages (yes, even more&lt;br /&gt;
dependencies!) to OpenLC in order to support this&lt;br /&gt;
new file formats. Sorry for the (hopefully small)&lt;br /&gt;
inconvenience!.&lt;/p&gt;
&lt;p&gt;Enjoy!&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>OpenLC 0.3 relased!</title><link href="https://sourceforge.net/p/openlc/news/2001/10/openlc-03-relased/" rel="alternate"/><published>2001-10-30T19:17:41Z</published><updated>2001-10-30T19:17:41Z</updated><author><name>Francesc Altet</name><uri>https://sourceforge.net/u/falted/</uri></author><id>https://sourceforge.net1e6decaa33219ca3f43ddc3076438fad21ee8236</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;OpenLC is a set of software tools designed to facilitate benchmarking and stress testing of a wide variety of information servers (such as web, email, FTP, LDAP, databases, and so on). The package is built around a microkernel that contains basic routines for benchmarking tasks, such as accessing intermediate results in real-time (&amp;quot;spying&amp;quot; on run data), setting up simulated clients, defining scenarios, handling database calls, comparing results of different runs, summarizing data, etc.&lt;/p&gt;
&lt;p&gt;OpenLC also offers an API for developers interested in creating clients (called &amp;quot;commanders&amp;quot;, to distinguish them from the simulated client inside the microkernel) that query services provided within the microkernel.&lt;/p&gt;
&lt;p&gt;This is version 0.3 and first public release&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>