<?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: Ning Content Store</title>
	<atom:link href="http://crschmidt.net/blog/98/ning-content-store/feed/" rel="self" type="application/rss+xml" />
	<link>http://crschmidt.net/blog/98/ning-content-store/</link>
	<description>Ramblings of a GIS Hacker</description>
	<pubDate>Thu, 04 Dec 2008 01:07:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Christopher Schmidt</title>
		<link>http://crschmidt.net/blog/98/ning-content-store/#comment-3848</link>
		<dc:creator>Christopher Schmidt</dc:creator>
		<pubDate>Wed, 05 Oct 2005 19:54:38 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/98/ning-content-store/#comment-3848</guid>
		<description>Martin: To be totally honest, I know absolutely nothing about the backend of the Ning Content Store, or most of the Ning architecture. I haven't participated in most of the backend development: my work has been in building apps and making sure that they're as awesome as possible. 

However, I do know that they have some really smart people working for them, so I'm not stressed about scalability long term. (They may find some bugs as things start to get bigger, as everyone does, but I am confident they've built an awesome team of people who will be able to fix it.) Like I said, how you get to data doesn't matter so long as it works, and I think that this is something which I'm convinced will work.</description>
		<content:encoded><![CDATA[<p>Martin: To be totally honest, I know absolutely nothing about the backend of the Ning Content Store, or most of the Ning architecture. I haven&#8217;t participated in most of the backend development: my work has been in building apps and making sure that they&#8217;re as awesome as possible. </p>
<p>However, I do know that they have some really smart people working for them, so I&#8217;m not stressed about scalability long term. (They may find some bugs as things start to get bigger, as everyone does, but I am confident they&#8217;ve built an awesome team of people who will be able to fix it.) Like I said, how you get to data doesn&#8217;t matter so long as it works, and I think that this is something which I&#8217;m convinced will work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin May</title>
		<link>http://crschmidt.net/blog/98/ning-content-store/#comment-3847</link>
		<dc:creator>Martin May</dc:creator>
		<pubDate>Wed, 05 Oct 2005 19:44:32 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/98/ning-content-store/#comment-3847</guid>
		<description>Good post that sheds some more light on the Ning Content Store. I'm curious about what you use as a backend for the content store, and how you are planning to scale it.

Could you talk a little about that, or is that confidential information?

Thanks,
Martin</description>
		<content:encoded><![CDATA[<p>Good post that sheds some more light on the Ning Content Store. I&#8217;m curious about what you use as a backend for the content store, and how you are planning to scale it.</p>
<p>Could you talk a little about that, or is that confidential information?</p>
<p>Thanks,<br />
Martin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Semantic Wave</title>
		<link>http://crschmidt.net/blog/98/ning-content-store/#comment-3846</link>
		<dc:creator>Semantic Wave</dc:creator>
		<pubDate>Wed, 05 Oct 2005 19:28:17 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/98/ning-content-store/#comment-3846</guid>
		<description>&lt;strong&gt;Ning Content Store&lt;/strong&gt;

Chris covers this subject in much more detail, but I'll post anyway. I was looking around Ning (perhaps Ning around?) and noticed an interesting blog entry about the Ning Content Store. This hosting service provides its community with "data playdough...</description>
		<content:encoded><![CDATA[<p><strong>Ning Content Store</strong></p>
<p>Chris covers this subject in much more detail, but I&#8217;ll post anyway. I was looking around Ning (perhaps Ning around?) and noticed an interesting blog entry about the Ning Content Store. This hosting service provides its community with &#8220;data playdough&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
