<?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: Multi-User Listotron Prototype</title>
	<atom:link href="http://blog.listotron.com/2008/10/04/mult-user-listotron-prototype/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.listotron.com/2008/10/04/mult-user-listotron-prototype/</link>
	<description>The development blog for Listotron!</description>
	<lastBuildDate>Sun, 29 Nov 2009 07:44:28 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: adam</title>
		<link>http://blog.listotron.com/2008/10/04/mult-user-listotron-prototype/comment-page-1/#comment-23</link>
		<dc:creator>adam</dc:creator>
		<pubDate>Mon, 08 Dec 2008 16:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.listotron.com/?p=50#comment-23</guid>
		<description>yeah - people will be able to edit the same row at the same time. We&#039;ll show a color marker of some sort to let you know that someone else is editing that row as well, but we&#039;ll allow it.

In the final version, we&#039;ll also have multiple columns, so people will be able to edit different columns/same row no problem.

if two people edit the same row and same column at the same time, the resolution is simply who-ever gets their last wins. The most recent edit will always prevail. for the guy who got their milliseconds too soon, their edit will still be in the global undo history for the list, so it&#039;s recoverable if it really needs to be.</description>
		<content:encoded><![CDATA[<p>yeah &#8211; people will be able to edit the same row at the same time. We&#8217;ll show a color marker of some sort to let you know that someone else is editing that row as well, but we&#8217;ll allow it.</p>
<p>In the final version, we&#8217;ll also have multiple columns, so people will be able to edit different columns/same row no problem.</p>
<p>if two people edit the same row and same column at the same time, the resolution is simply who-ever gets their last wins. The most recent edit will always prevail. for the guy who got their milliseconds too soon, their edit will still be in the global undo history for the list, so it&#8217;s recoverable if it really needs to be.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Ruckman</title>
		<link>http://blog.listotron.com/2008/10/04/mult-user-listotron-prototype/comment-page-1/#comment-22</link>
		<dc:creator>Justin Ruckman</dc:creator>
		<pubDate>Wed, 03 Dec 2008 19:21:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.listotron.com/?p=50#comment-22</guid>
		<description>I&#039;ve wanted this kind of basic functionality in a webapp for awhile now. But I&#039;m curious, how do you resolve revision conflicts? Can two people edit the same line at the same time?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve wanted this kind of basic functionality in a webapp for awhile now. But I&#8217;m curious, how do you resolve revision conflicts? Can two people edit the same line at the same time?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Listotron Prototype &#124; Wulf</title>
		<link>http://blog.listotron.com/2008/10/04/mult-user-listotron-prototype/comment-page-1/#comment-17</link>
		<dc:creator>Listotron Prototype &#124; Wulf</dc:creator>
		<pubDate>Sat, 04 Oct 2008 07:26:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.listotron.com/?p=50#comment-17</guid>
		<description>[...] over to the Listotron blog and check out the short demo video of the first Listotron prototype! Can anyone say [...]</description>
		<content:encoded><![CDATA[<p>[...] over to the Listotron blog and check out the short demo video of the first Listotron prototype! Can anyone say [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.731 seconds -->

<!-- Page not cached by WP Super Cache. Could not get mutex lock. -->
