<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Caching Completed</title>
	<link>http://mvblogs.org/blog/10</link>
	<description>Documentation of the of project development process</description>
	<pubDate>Mon, 06 Feb 2012 04:01:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: Inn</title>
		<link>http://mvblogs.org/blog/10#comment-11</link>
		<author>Inn</author>
		<pubDate>Wed, 18 Jan 2006 03:20:56 +0000</pubDate>
		<guid>http://mvblogs.org/blog/10#comment-11</guid>
		<description>&lt;p&gt;Sorry I couldn't disclose those information. So here it is. The number of entries cached is not displayed in the 'Latest Updated' page, but I will be updating it. The number of entries displayed is the number of entries cached.&lt;/p&gt;
&lt;p&gt;The caching process truncates the content of each entry to 310 characters. I think we should change it to grab 'n' number of words instead of characters since it will be more elegant that way and it will fix the problem with truncating in the middle of an ending word.&lt;/p&gt;
&lt;p&gt;How we came up with these? We thought them of as the basic requirements for a system like this. displaying the necessary information just to keep it up to date. A database that provides static information won't be very useful unless it implements a dynamic feature that will render it's usage valuable.&lt;/p&gt;
&lt;p&gt;So here it is. The system is now feature complete. We can call this version 1.0 beta since there are (and will be) a couple of bugs every here and there.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Sorry I couldn&#8217;t disclose those information. So here it is. The number of entries cached is not displayed in the &#8216;Latest Updated&#8217; page, but I will be updating it. The number of entries displayed is the number of entries cached.</p>
<p>The caching process truncates the content of each entry to 310 characters. I think we should change it to grab &#8216;n&#8217; number of words instead of characters since it will be more elegant that way and it will fix the problem with truncating in the middle of an ending word.</p>
<p>How we came up with these? We thought them of as the basic requirements for a system like this. displaying the necessary information just to keep it up to date. A database that provides static information won&#8217;t be very useful unless it implements a dynamic feature that will render it&#8217;s usage valuable.</p>
<p>So here it is. The system is now feature complete. We can call this version 1.0 beta since there are (and will be) a couple of bugs every here and there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shahee</title>
		<link>http://mvblogs.org/blog/10#comment-10</link>
		<author>Shahee</author>
		<pubDate>Wed, 18 Jan 2006 02:57:23 +0000</pubDate>
		<guid>http://mvblogs.org/blog/10#comment-10</guid>
		<description>How many entries are cached, and how many are displayed? Also, how many words from each post is displayed? How did you you (and the team) come up with these?</description>
		<content:encoded><![CDATA[<p>How many entries are cached, and how many are displayed? Also, how many words from each post is displayed? How did you you (and the team) come up with these?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

