<?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"
	>
<channel>
	<title>Comments on: Memcache, keeping data in the handiest place: memory</title>
	<atom:link href="http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory/feed" rel="self" type="application/rss+xml" />
	<link>http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory</link>
	<description>A permanent record for what's interesting today - this is my live journal</description>
	<pubDate>Wed, 08 Oct 2008 07:01:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Dustin</title>
		<link>http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory#comment-136348</link>
		<dc:creator>Dustin</dc:creator>
		<pubDate>Sun, 05 Oct 2008 05:04:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory#comment-136348</guid>
		<description>Just for clarity (since this has come up on the list), every memcached operation is atomic, but the cache is not transactional.  The CAS operation exists in the text protocol for performing an atomic read/update operation, and is extended to every operation in the binary protocol.</description>
		<content:encoded><![CDATA[<p>Just for clarity (since this has come up on the list), every memcached operation is atomic, but the cache is not transactional.  The CAS operation exists in the text protocol for performing an atomic read/update operation, and is extended to every operation in the binary protocol.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dustin</title>
		<link>http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory#comment-136347</link>
		<dc:creator>Dustin</dc:creator>
		<pubDate>Sun, 05 Oct 2008 05:03:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory#comment-136347</guid>
		<description>Just for clarity (since this has come up on the list), every memcached operation is atomic, but</description>
		<content:encoded><![CDATA[<p>Just for clarity (since this has come up on the list), every memcached operation is atomic, but</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colin Charles Agenda &#187; Blog Archive &#187; MySQL Miniconf videos, from linux.conf.au 2008</title>
		<link>http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory#comment-131744</link>
		<dc:creator>Colin Charles Agenda &#187; Blog Archive &#187; MySQL Miniconf videos, from linux.conf.au 2008</dc:creator>
		<pubDate>Thu, 14 Feb 2008 16:54:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory#comment-131744</guid>
		<description>[...] offer. I&#8217;m surprised the LinuxChix talks never made it online (there was a really interesting memcache talk [...]</description>
		<content:encoded><![CDATA[<p>[...] offer. I&#8217;m surprised the LinuxChix talks never made it online (there was a really interesting memcache talk [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oliver</title>
		<link>http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory#comment-131221</link>
		<dc:creator>Oliver</dc:creator>
		<pubDate>Wed, 30 Jan 2008 00:37:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory#comment-131221</guid>
		<description>Memcache doesn't have locks, though its increase/decrease methods are atomic! This way you can easily create locks in your own code.

To me thats a really important feature, thought its worth mentioning it.</description>
		<content:encoded><![CDATA[<p>Memcache doesn&#8217;t have locks, though its increase/decrease methods are atomic! This way you can easily create locks in your own code.</p>
<p>To me thats a really important feature, thought its worth mentioning it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: colin</title>
		<link>http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory#comment-131184</link>
		<dc:creator>colin</dc:creator>
		<pubDate>Tue, 29 Jan 2008 04:02:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory#comment-131184</guid>
		<description>Haha, good point Simon. I think MySQL (the company) is still fixing mistakes of the past. We fixed a lot of complaints in 5.0, but said a bunch of silly things before. Give us another chance, it is after all 2008 :)</description>
		<content:encoded><![CDATA[<p>Haha, good point Simon. I think MySQL (the company) is still fixing mistakes of the past. We fixed a lot of complaints in 5.0, but said a bunch of silly things before. Give us another chance, it is after all 2008 :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Rumble</title>
		<link>http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory#comment-131182</link>
		<dc:creator>Simon Rumble</dc:creator>
		<pubDate>Tue, 29 Jan 2008 03:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory#comment-131182</guid>
		<description>Was just a gentle dig.  Remember that until 2001 it didn't support referential integrity or transactions and the developers claimed these things were bad ideas...  Just doesn't give me much faith.

As for "the most widely used..." -- Windows is the most widely used desktop OS, and lookit that ;)</description>
		<content:encoded><![CDATA[<p>Was just a gentle dig.  Remember that until 2001 it didn&#8217;t support referential integrity or transactions and the developers claimed these things were bad ideas&#8230;  Just doesn&#8217;t give me much faith.</p>
<p>As for &#8220;the most widely used&#8230;&#8221; &#8212; Windows is the most widely used desktop OS, and lookit that ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: byte</title>
		<link>http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory#comment-131180</link>
		<dc:creator>byte</dc:creator>
		<pubDate>Tue, 29 Jan 2008 03:12:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory#comment-131180</guid>
		<description>Erm, MySQL supports referential integrity, for a while now Simon. And saying its not a database, or reliable, is rather silly, no? Seeing that its probably the most widely used open source database out there (you know, Google, Yahoo!, etc.). I suggest taking a look at a sensible, newer release, in the MySQL 5 range (and if you're brave, the 5.1 RC)</description>
		<content:encoded><![CDATA[<p>Erm, MySQL supports referential integrity, for a while now Simon. And saying its not a database, or reliable, is rather silly, no? Seeing that its probably the most widely used open source database out there (you know, Google, Yahoo!, etc.). I suggest taking a look at a sensible, newer release, in the MySQL 5 range (and if you&#8217;re brave, the 5.1 RC)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Rumble</title>
		<link>http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory#comment-131179</link>
		<dc:creator>Simon Rumble</dc:creator>
		<pubDate>Tue, 29 Jan 2008 02:51:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytebot.net/blog/archives/2008/01/28/memcache-keeping-data-in-the-handiest-place-memory#comment-131179</guid>
		<description>"No check for validity. No referential integrity, its not a database."

So about as reliable as MySQL then.  </description>
		<content:encoded><![CDATA[<p>&#8220;No check for validity. No referential integrity, its not a database.&#8221;</p>
<p>So about as reliable as MySQL then.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
