<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 109: Rework check available and chunk allocation</title><link>https://sourceforge.net/p/objectify/feature-requests/109/</link><description>Recent changes to 109: Rework check available and chunk allocation</description><atom:link href="https://sourceforge.net/p/objectify/feature-requests/109/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 28 Oct 2008 13:47:01 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/objectify/feature-requests/109/feed.rss" rel="self" type="application/rss+xml"/><item><title>Rework check available and chunk allocation</title><link>https://sourceforge.net/p/objectify/feature-requests/109/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Rework the entire check for available blocks and chunk allocation code.&lt;/p&gt;
&lt;p&gt;Why does the check blocks available allocate the chunks?  Wouldn't it be better to allocate them as the reference IDs are generated?  Have the check blocks available function just verify that there is enough storage in a form that will work.&lt;/p&gt;
&lt;p&gt;Maybe it should try to randomize even in minimal if all of the existing chunks are too dense? &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">J. Scott Edwards</dc:creator><pubDate>Tue, 28 Oct 2008 13:47:01 -0000</pubDate><guid>https://sourceforge.net01d81ac6b0dd3dca011803878c89dbc749117a93</guid></item></channel></rss>