<?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: 5 Reasons to avoid multi-year colocation contracts</title>
	<atom:link href="http://www.ebusinessblog.org/32/5-reasons-to-avoid-multi-year-colocation-contracts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ebusinessblog.org/32/5-reasons-to-avoid-multi-year-colocation-contracts/</link>
	<description>Leveraging marketing &#38; technology to solve business problems.</description>
	<lastBuildDate>Tue, 03 Jan 2012 04:25:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: negate.net &#187; apache mod_deflate reduces bandwidth usage by 27% on SuperMotors.net</title>
		<link>http://www.ebusinessblog.org/32/5-reasons-to-avoid-multi-year-colocation-contracts/comment-page-1/#comment-4</link>
		<dc:creator>negate.net &#187; apache mod_deflate reduces bandwidth usage by 27% on SuperMotors.net</dc:creator>
		<pubDate>Sat, 02 Dec 2006 16:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.negate.net/32/tech/5-reasons-to-avoid-multi-year-colocation-contracts/#comment-4</guid>
		<description>[...] This bandwidth reduction is very good news for us. As previously posted, we are leaving the world of colocation and moving to managed hosting &#8212; with a new billing model. The &#8220;total bandwidth used&#8221; billing model favors us even more now that we&#8217;ve reduced bandwidth usage by 27%. This translates into squeezing more data out of the pipe that previously anticipated. We&#8217;ll be able to maintain our fixed costs and increase revenue, thanks to this little module. The more data we push out, the more page views we serve, and the more revenue we make from our CPM-based advertising model with Tribal Fusion and our in-house ad inventory (read the challenges we face when we introduce Ajax functionality and how it&#8217;ll affect our CPM-based ad model). [...]</description>
		<content:encoded><![CDATA[<p>[...] This bandwidth reduction is very good news for us. As previously posted, we are leaving the world of colocation and moving to managed hosting &#8212; with a new billing model. The &#8220;total bandwidth used&#8221; billing model favors us even more now that we&#8217;ve reduced bandwidth usage by 27%. This translates into squeezing more data out of the pipe that previously anticipated. We&#8217;ll be able to maintain our fixed costs and increase revenue, thanks to this little module. The more data we push out, the more page views we serve, and the more revenue we make from our CPM-based advertising model with Tribal Fusion and our in-house ad inventory (read the challenges we face when we introduce Ajax functionality and how it&#8217;ll affect our CPM-based ad model). [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

