<?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 for server says</title>
	<atom:link href="http://trentdv.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://trentdv.com</link>
	<description>what server says goes</description>
	<pubDate>Wed, 03 Dec 2008 22:52:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-beta3-9922</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Hardware Upgrade by trent</title>
		<link>http://trentdv.com/2008/06/06/hardware-upgrade/comment-page-1/#comment-5</link>
		<dc:creator>trent</dc:creator>
		<pubDate>Sat, 07 Jun 2008 00:07:56 +0000</pubDate>
		<guid isPermaLink="false">http://trentdv.com/?p=19#comment-5</guid>
		<description>The update is now complete and all services should be restored.</description>
		<content:encoded><![CDATA[<p>The update is now complete and all services should be restored.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Upcoming WPMU 1.5 Upgrade by trent</title>
		<link>http://trentdv.com/2008/04/20/upcoming-wpmu-15-upgrade/comment-page-1/#comment-2</link>
		<dc:creator>trent</dc:creator>
		<pubDate>Thu, 08 May 2008 16:33:44 +0000</pubDate>
		<guid isPermaLink="false">http://trentdv.onvertigo.com/2008/04/20/upcoming-wpmu-15-upgrade/#comment-2</guid>
		<description>There were a couple of changes made to WPMU 1.5 before the release and I am sure there are a couple more, but we tested them on our testbed and they were fine, so we are officially using the latest version without problems.</description>
		<content:encoded><![CDATA[<p>There were a couple of changes made to WPMU 1.5 before the release and I am sure there are a couple more, but we tested them on our testbed and they were fine, so we are officially using the latest version without problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Database Redundancy by trent</title>
		<link>http://trentdv.com/2008/04/26/database-redundancy/comment-page-1/#comment-4</link>
		<dc:creator>trent</dc:creator>
		<pubDate>Fri, 02 May 2008 23:41:47 +0000</pubDate>
		<guid isPermaLink="false">http://trentdv.onvertigo.com/2008/04/26/database-redundancy/#comment-4</guid>
		<description>Quicker than expected we have this working now with our database redundancy now on another (dv) server at Media Temple.   It is working great!</description>
		<content:encoded><![CDATA[<p>Quicker than expected we have this working now with our database redundancy now on another (dv) server at Media Temple.   It is working great!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Database Redundancy by trent</title>
		<link>http://trentdv.com/2008/04/26/database-redundancy/comment-page-1/#comment-3</link>
		<dc:creator>trent</dc:creator>
		<pubDate>Fri, 02 May 2008 15:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://trentdv.onvertigo.com/2008/04/26/database-redundancy/#comment-3</guid>
		<description>After playing around with "slicehost", we decided that it might be an easier transition to start up our replication on another Media Temple server.   While slicehost is a great host and a small amount cheaper, our administration, support, security and consistency with another (dv) server is the better fit.    It will take a bit more time before we implement our solutions, but we are looking forward to the changes!</description>
		<content:encoded><![CDATA[<p>After playing around with &#8220;slicehost&#8221;, we decided that it might be an easier transition to start up our replication on another Media Temple server.   While slicehost is a great host and a small amount cheaper, our administration, support, security and consistency with another (dv) server is the better fit.    It will take a bit more time before we implement our solutions, but we are looking forward to the changes!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
