<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Misc on ftp.fau.de news and statistics</title>
		<link>https://ftp.fau.de/news/tags/misc/</link>
		<description>Recent content in Misc on ftp.fau.de news and statistics</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 11 Apr 2016 12:00:00 +0200</lastBuildDate>
		
			<atom:link href="https://ftp.fau.de/news/tags/misc/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Evaluating Project Mirroring by Cost vs Profit</title>
				<link>https://ftp.fau.de/news/posts/evaluating-project-mirroring-by-cost-vs-profit/</link>
				<pubDate>Mon, 11 Apr 2016 12:00:00 +0200</pubDate>
				<guid>https://ftp.fau.de/news/posts/evaluating-project-mirroring-by-cost-vs-profit/</guid>
				<description>&lt;p&gt;People operate mirrors out of different reasons, this could be purely altruistic to support open source communities, or to reduce incoming traffic by providing local clients with an internal package source, or to tilt the in/out ratio of the internet uplink. What ever the reasons are, they are all associated with the usage of outbound traffic and local storage size, in addition to occupation of other hardware and administrative resources. We will consider traffic and storage requirements as the costs and outgoing traffic as the profit (to the general public or an organization) a mirror service provides.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
