<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: More OpenDSM pointers</title>
	<link>http://blogs.educationau.edu.au/nlothian/2008/02/21/more-opendsm-pointers/</link>
	<description>Nick's Education.au Weblog</description>
	<pubDate>Wed, 07 Jan 2009 23:23:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Simon</title>
		<link>http://blogs.educationau.edu.au/nlothian/2008/02/21/more-opendsm-pointers/#comment-57246</link>
		<pubDate>Tue, 27 May 2008 02:24:49 +0000</pubDate>
		<guid>http://blogs.educationau.edu.au/nlothian/2008/02/21/more-opendsm-pointers/#comment-57246</guid>
					<description>Nice description of the 'wait' strategies there, Nick.  A new one currently being added to the mix is the "waitfor" strategy which instructs openDSM to wait for nominated repositories before showing any results (there is of course a max-time-to-wait param with that).  So if you have key repositories then you can be sure they are shown on first view, without having to still wait for the slower ones.  This will be released in the next couple weeks.</description>
		<content:encoded><![CDATA[<p>Nice description of the &#8216;wait&#8217; strategies there, Nick.  A new one currently being added to the mix is the &#8220;waitfor&#8221; strategy which instructs openDSM to wait for nominated repositories before showing any results (there is of course a max-time-to-wait param with that).  So if you have key repositories then you can be sure they are shown on first view, without having to still wait for the slower ones.  This will be released in the next couple weeks.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
