<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: From the dark corners of being on holiday &#8230;</title>
	<atom:link href="http://pvanhoof.be/blog/index.php/2007/08/28/from-the-dark-corners-of-being-on-holiday/feed" rel="self" type="application/rss+xml" />
	<link>http://pvanhoof.be/blog/index.php/2007/08/28/from-the-dark-corners-of-being-on-holiday</link>
	<description>From the mind of Philip</description>
	<lastBuildDate>Sun, 28 Aug 2011 12:59:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: pvanhoof</title>
		<link>http://pvanhoof.be/blog/index.php/2007/08/28/from-the-dark-corners-of-being-on-holiday#comment-409</link>
		<dc:creator>pvanhoof</dc:creator>
		<pubDate>Tue, 28 Aug 2007 22:58:49 +0000</pubDate>
		<guid isPermaLink="false">http://pvanhoof.be/blog/index.php/2007/08/28/from-the-dark-corners-of-being-on-holiday#comment-409</guid>
		<description>For that you don&#039;t really need to structure the in-memory version of that information as a bunch of pointers to the strings who are those references. Just for each unique string keep a quark (a unique number) and store that in the summary items. Or something like that.

This of course means retrieving the information, converting it to these quarks and then storing it consistently (in the same way between sessions).

Well, I of course welcome your contribution that makes this a sortable field, mgedmin :-). If you have questions about re-enabling the downloading of this field, just ask.</description>
		<content:encoded><![CDATA[<p>For that you don&#8217;t really need to structure the in-memory version of that information as a bunch of pointers to the strings who are those references. Just for each unique string keep a quark (a unique number) and store that in the summary items. Or something like that.</p>
<p>This of course means retrieving the information, converting it to these quarks and then storing it consistently (in the same way between sessions).</p>
<p>Well, I of course welcome your contribution that makes this a sortable field, mgedmin :-). If you have questions about re-enabling the downloading of this field, just ask.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mgedmin</title>
		<link>http://pvanhoof.be/blog/index.php/2007/08/28/from-the-dark-corners-of-being-on-holiday#comment-410</link>
		<dc:creator>mgedmin</dc:creator>
		<pubDate>Tue, 28 Aug 2007 21:24:04 +0000</pubDate>
		<guid isPermaLink="false">http://pvanhoof.be/blog/index.php/2007/08/28/from-the-dark-corners-of-being-on-holiday#comment-410</guid>
		<description>There&#039;s a very good reason to do threading even if you are not going to show the tree to the user: proper ordering of messages.  When you have a big discussion thread with multiple simultaneous subthreads going on, grouping by subject then sorting by date won&#039;t work.</description>
		<content:encoded><![CDATA[<p>There&#8217;s a very good reason to do threading even if you are not going to show the tree to the user: proper ordering of messages.  When you have a big discussion thread with multiple simultaneous subthreads going on, grouping by subject then sorting by date won&#8217;t work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

