<?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: Network Support for Lightroom</title>
	<atom:link href="http://www.allengambrell.com/2008/04/09/network-support-for-lightroom/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.allengambrell.com/2008/04/09/network-support-for-lightroom/</link>
	<description>Some very very random thoughts!</description>
	<lastBuildDate>Wed, 23 Jun 2010 04:20:41 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tyler Havener</title>
		<link>http://www.allengambrell.com/2008/04/09/network-support-for-lightroom/comment-page-1/#comment-100</link>
		<dc:creator>Tyler Havener</dc:creator>
		<pubDate>Tue, 23 Mar 2010 16:59:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.allengambrell.com/?p=6#comment-100</guid>
		<description>Adobe is stupid. Just create a hidden/external lock file next to the catalog file (in the same folder as), to indicate it is being edited, with a username and computer name in it. Delete the file when you&#039;re out of the catalog.

The program just checks to see if it exists when the catalog is opened and displays a warning, with an option to override in case it is orphaned.  The lock file can be used in addition to any locking mechanism the network resource provides.

This would be a very club-footed approach, but is workable. Network users can work out whether or not the files are open or in use. The truth is, in small environments, this is not a problem.

Oh, and there are countless solutions that play nice on the network. iView, anyone? (now expression media)</description>
		<content:encoded><![CDATA[<p>Adobe is stupid. Just create a hidden/external lock file next to the catalog file (in the same folder as), to indicate it is being edited, with a username and computer name in it. Delete the file when you&#8217;re out of the catalog.</p>
<p>The program just checks to see if it exists when the catalog is opened and displays a warning, with an option to override in case it is orphaned.  The lock file can be used in addition to any locking mechanism the network resource provides.</p>
<p>This would be a very club-footed approach, but is workable. Network users can work out whether or not the files are open or in use. The truth is, in small environments, this is not a problem.</p>
<p>Oh, and there are countless solutions that play nice on the network. iView, anyone? (now expression media)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allen</title>
		<link>http://www.allengambrell.com/2008/04/09/network-support-for-lightroom/comment-page-1/#comment-59</link>
		<dc:creator>Allen</dc:creator>
		<pubDate>Fri, 14 Aug 2009 15:04:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.allengambrell.com/?p=6#comment-59</guid>
		<description>I have used the subst command, and it will corrupt your lightroom catalog.</description>
		<content:encoded><![CDATA[<p>I have used the subst command, and it will corrupt your lightroom catalog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shannon</title>
		<link>http://www.allengambrell.com/2008/04/09/network-support-for-lightroom/comment-page-1/#comment-58</link>
		<dc:creator>Shannon</dc:creator>
		<pubDate>Thu, 13 Aug 2009 21:05:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.allengambrell.com/?p=6#comment-58</guid>
		<description>You can actually use &quot;subst&quot; command to map a local drive letter to your network drive. Fools Lightroom and works like a charm!</description>
		<content:encoded><![CDATA[<p>You can actually use &#8220;subst&#8221; command to map a local drive letter to your network drive. Fools Lightroom and works like a charm!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
