<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Hoping for an Apple media server</title>
	<atom:link href="http://blogs.reuters.com/felix-salmon/2009/05/26/hoping-for-an-apple-media-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.reuters.com/felix-salmon/2009/05/26/hoping-for-an-apple-media-server/</link>
	<description>A slice of lime in the soda</description>
	<lastBuildDate>Thu, 20 Jun 2013 02:11:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: bill</title>
		<link>http://blogs.reuters.com/felix-salmon/2009/05/26/hoping-for-an-apple-media-server/comment-page-1/#comment-2050</link>
		<dc:creator>bill</dc:creator>
		<pubDate>Wed, 27 May 2009 17:35:03 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reuters.com/felix-salmon/2009/05/26/hoping-for-an-apple-media-server/#comment-2050</guid>
		<description>YEAH!!!!!!  I second, third and fourth this!!!  Go Felix!  

Apple has no choice.  They can&#039;t ignore media storage and leverage their installed base without offering an easy and simple to use storage option with multiple access methods across their hardware mac/pod/phone(s).  Anyone using their product(s) are running out of space rapidly.</description>
		<content:encoded><![CDATA[<p>YEAH!!!!!!  I second, third and fourth this!!!  Go Felix!  </p>
<p>Apple has no choice.  They can&#8217;t ignore media storage and leverage their installed base without offering an easy and simple to use storage option with multiple access methods across their hardware mac/pod/phone(s).  Anyone using their product(s) are running out of space rapidly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TW Andrews</title>
		<link>http://blogs.reuters.com/felix-salmon/2009/05/26/hoping-for-an-apple-media-server/comment-page-1/#comment-1993</link>
		<dc:creator>TW Andrews</dc:creator>
		<pubDate>Tue, 26 May 2009 20:07:29 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reuters.com/felix-salmon/2009/05/26/hoping-for-an-apple-media-server/#comment-1993</guid>
		<description>Amen! It&#039;s exactly this difficulty that prevents me from moving to macs in general.</description>
		<content:encoded><![CDATA[<p>Amen! It&#8217;s exactly this difficulty that prevents me from moving to macs in general.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: macsyscat</title>
		<link>http://blogs.reuters.com/felix-salmon/2009/05/26/hoping-for-an-apple-media-server/comment-page-1/#comment-1990</link>
		<dc:creator>macsyscat</dc:creator>
		<pubDate>Tue, 26 May 2009 19:20:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reuters.com/felix-salmon/2009/05/26/hoping-for-an-apple-media-server/#comment-1990</guid>
		<description>This opens a window into shared file systems.  A file opened for read/write needs to be locked for multi-user access until the update is complete. Failure to do this corrupts the data base. One could make a subset for read-only but then updates are still problematic.
Physical disk location has never been a problem on macs due to its unix foundation but files can never span disks (Raids are physical beasts that present one huge disk to the operating system). Moving iTunes to a bigger disk  is a simple library copy followed by an index rebuild. 
Owner rights are always functioning and updating a shared disk has to take that into account. If someone places a new song or photo in a library and fails to allow world access it remains unseen.
Multi-user security and group/world read/write access are always in conflict.</description>
		<content:encoded><![CDATA[<p>This opens a window into shared file systems.  A file opened for read/write needs to be locked for multi-user access until the update is complete. Failure to do this corrupts the data base. One could make a subset for read-only but then updates are still problematic.<br />
Physical disk location has never been a problem on macs due to its unix foundation but files can never span disks (Raids are physical beasts that present one huge disk to the operating system). Moving iTunes to a bigger disk  is a simple library copy followed by an index rebuild.<br />
Owner rights are always functioning and updating a shared disk has to take that into account. If someone places a new song or photo in a library and fails to allow world access it remains unseen.<br />
Multi-user security and group/world read/write access are always in conflict.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jose Trujillo</title>
		<link>http://blogs.reuters.com/felix-salmon/2009/05/26/hoping-for-an-apple-media-server/comment-page-1/#comment-1974</link>
		<dc:creator>Jose Trujillo</dc:creator>
		<pubDate>Tue, 26 May 2009 17:27:10 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reuters.com/felix-salmon/2009/05/26/hoping-for-an-apple-media-server/#comment-1974</guid>
		<description>Yes I agree I use a alias of my iTunes music folder with the linking folder stored on an external but already need to upgrade to a larger hard drive.  

something similar to this 
MobileNAS MN2L - 2 Bay RAID 0 / RAID 1 Network Attached Storage NAS Server

http://www.sansdigital.com/mobilenas/mn2l.html 

would be a good starting point for Apple.</description>
		<content:encoded><![CDATA[<p>Yes I agree I use a alias of my iTunes music folder with the linking folder stored on an external but already need to upgrade to a larger hard drive.  </p>
<p>something similar to this<br />
MobileNAS MN2L &#8211; 2 Bay RAID 0 / RAID 1 Network Attached Storage NAS Server</p>
<p><a href='http://www.sansdigital.com/mobilenas/mn2l.html'>http://www.sansdigital.com/mobilenas/mn2 l.html</a> </p>
<p>would be a good starting point for Apple.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
