<?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: iClone Twitter Updates for 2010-05-24</title>
	<atom:link href="http://www.iclone.org.uk/2010/05/iclone-twitter-updates-for-2010-05-24/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.iclone.org.uk/2010/05/iclone-twitter-updates-for-2010-05-24/</link>
	<description>iClone</description>
	<lastBuildDate>Sun, 31 Jul 2011 15:21:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: BenS</title>
		<link>http://www.iclone.org.uk/2010/05/iclone-twitter-updates-for-2010-05-24/comment-page-1/#comment-1022</link>
		<dc:creator>BenS</dc:creator>
		<pubDate>Wed, 16 Jun 2010 07:54:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.iclone.org.uk/2010/05/iclone-twitter-updates-for-2010-05-24/#comment-1022</guid>
		<description>Agreed the update load could be lightened - it&#039;s something I&#039;m looking at improving. The update just submitted for approval allows you to turn off individual characters, and automatically disables expired accounts. Some other code tweaks in the update *should* make the existing updates quicker - In my personal benchmarks big asset lists are now about twice as fast. The ability to turn off individual (trees of) updates is on the planned feature list, I just haven&#039;t formed a clear plan of attack yet - throwing a huge blob of switches at the user never seems like the right call!</description>
		<content:encoded><![CDATA[<p>Agreed the update load could be lightened &#8211; it&#8217;s something I&#8217;m looking at improving. The update just submitted for approval allows you to turn off individual characters, and automatically disables expired accounts. Some other code tweaks in the update *should* make the existing updates quicker &#8211; In my personal benchmarks big asset lists are now about twice as fast. The ability to turn off individual (trees of) updates is on the planned feature list, I just haven&#8217;t formed a clear plan of attack yet &#8211; throwing a huge blob of switches at the user never seems like the right call!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shin</title>
		<link>http://www.iclone.org.uk/2010/05/iclone-twitter-updates-for-2010-05-24/comment-page-1/#comment-877</link>
		<dc:creator>Shin</dc:creator>
		<pubDate>Wed, 26 May 2010 15:39:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.iclone.org.uk/2010/05/iclone-twitter-updates-for-2010-05-24/#comment-877</guid>
		<description>If you could have some sort of tab in the setting to either pick what you want to update, or remove certain updates to lighten the load and time, this ap would improve greatly, atm though it&#039;s a 10 minute+ slog to run four accounts.</description>
		<content:encoded><![CDATA[<p>If you could have some sort of tab in the setting to either pick what you want to update, or remove certain updates to lighten the load and time, this ap would improve greatly, atm though it&#8217;s a 10 minute+ slog to run four accounts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using apc
Database Caching 5/10 queries in 0.003 seconds using apc
Object Caching 318/319 objects using apc

Served from: www.iclone.org.uk @ 2012-02-08 18:50:47 -->
