<?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: The comprehensive guide to upgrading – or replacing – Twitter</title>
	<atom:link href="http://www.texttechnologies.com/2008/02/09/scalable-twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.texttechnologies.com/2008/02/09/scalable-twitter/</link>
	<description>Understanding technology ... in both senses of the phrase</description>
	<lastBuildDate>Mon, 25 Jan 2010 04:08:39 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Google Wave &#8212; finally a Microsoft killer? &#124; Text Technologies</title>
		<link>http://www.texttechnologies.com/2008/02/09/scalable-twitter/comment-page-1/#comment-100055</link>
		<dc:creator>Google Wave &#8212; finally a Microsoft killer? &#124; Text Technologies</dc:creator>
		<pubDate>Fri, 29 May 2009 09:49:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/2008/02/09/scalable-twitter/#comment-100055</guid>
		<description>[...] needs to be integrated with other forms of communication. What&#8217;s more, Twitter&#8217;s functionality needs to be drastically extended. Google Wave is the best hope I know of to meet those needs.  Enterprise Twitter is just a special [...]</description>
		<content:encoded><![CDATA[<p>[...] needs to be integrated with other forms of communication. What&#8217;s more, Twitter&#8217;s functionality needs to be drastically extended. Google Wave is the best hope I know of to meet those needs.  Enterprise Twitter is just a special [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thoughts on the rumored Google/Twitter deal &#124; Text Technologies</title>
		<link>http://www.texttechnologies.com/2008/02/09/scalable-twitter/comment-page-1/#comment-76341</link>
		<dc:creator>Thoughts on the rumored Google/Twitter deal &#124; Text Technologies</dc:creator>
		<pubDate>Fri, 03 Apr 2009 06:57:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/2008/02/09/scalable-twitter/#comment-76341</guid>
		<description>[...] I&#8217;ve been suggesting all along that Twitter needs radical user experience enhancements. But when has Google ever made made user experience enhancements to a service? Its core search [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;ve been suggesting all along that Twitter needs radical user experience enhancements. But when has Google ever made made user experience enhancements to a service? Its core search [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The New Twitter : Social Media Mafia</title>
		<link>http://www.texttechnologies.com/2008/02/09/scalable-twitter/comment-page-1/#comment-50639</link>
		<dc:creator>The New Twitter : Social Media Mafia</dc:creator>
		<pubDate>Sat, 20 Sep 2008 10:31:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/2008/02/09/scalable-twitter/#comment-50639</guid>
		<description>[...] Text Technologies has an even more comprehensive guide of changes that they would like to see from Twitter which include, [...]</description>
		<content:encoded><![CDATA[<p>[...] Text Technologies has an even more comprehensive guide of changes that they would like to see from Twitter which include, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Communication, culture, and short text messages &#124; Text Technologies</title>
		<link>http://www.texttechnologies.com/2008/02/09/scalable-twitter/comment-page-1/#comment-44293</link>
		<dc:creator>Communication, culture, and short text messages &#124; Text Technologies</dc:creator>
		<pubDate>Mon, 07 Jul 2008 04:37:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/2008/02/09/scalable-twitter/#comment-44293</guid>
		<description>[...] advocated recently for increased use both of simple instant messaging and filtered microblogging. The main reason I like short text messages so much is that, at least in theory, they improve on [...]</description>
		<content:encoded><![CDATA[<p>[...] advocated recently for increased use both of simple instant messaging and filtered microblogging. The main reason I like short text messages so much is that, at least in theory, they improve on [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Text Technologies &#187; Blog Archive</title>
		<link>http://www.texttechnologies.com/2008/02/09/scalable-twitter/comment-page-1/#comment-38437</link>
		<dc:creator>Text Technologies &#187; Blog Archive</dc:creator>
		<pubDate>Fri, 25 Apr 2008 15:49:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/2008/02/09/scalable-twitter/#comment-38437</guid>
		<description>[...] Twitter&#8217;s case, a mass-successful form will necessarily look utterly different from what exists today.  Techie early-adopters are not going to recruit a critical mass of users into a system that [...]</description>
		<content:encoded><![CDATA[<p>[...] Twitter&#8217;s case, a mass-successful form will necessarily look utterly different from what exists today.  Techie early-adopters are not going to recruit a critical mass of users into a system that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DBMS2 &#8212; DataBase Management System Services &#187; Blog Archive &#187; More Twitter weirdness</title>
		<link>http://www.texttechnologies.com/2008/02/09/scalable-twitter/comment-page-1/#comment-38422</link>
		<dc:creator>DBMS2 &#8212; DataBase Management System Services &#187; Blog Archive &#187; More Twitter weirdness</dc:creator>
		<pubDate>Fri, 25 Apr 2008 04:11:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/2008/02/09/scalable-twitter/#comment-38422</guid>
		<description>[...] Twitter commonly has the problem of duplicate tweets. That is, if you post a message, it shows up twice. After a little while, the dupe disappears, but if you delete the dupe manually, the original is gone too. [...]</description>
		<content:encoded><![CDATA[<p>[...] Twitter commonly has the problem of duplicate tweets. That is, if you post a message, it shows up twice. After a little while, the dupe disappears, but if you delete the dupe manually, the original is gone too. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: More Twitter weirdness : e-Spot.se</title>
		<link>http://www.texttechnologies.com/2008/02/09/scalable-twitter/comment-page-1/#comment-36060</link>
		<dc:creator>More Twitter weirdness : e-Spot.se</dc:creator>
		<pubDate>Fri, 14 Mar 2008 08:26:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/2008/02/09/scalable-twitter/#comment-36060</guid>
		<description>[...] mars 2008  Twitter commonly has the problem of duplicate tweets. That is, if you post a message, it shows up twice. [...]</description>
		<content:encoded><![CDATA[<p>[...] mars 2008  Twitter commonly has the problem of duplicate tweets. That is, if you post a message, it shows up twice. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.texttechnologies.com/2008/02/09/scalable-twitter/comment-page-1/#comment-33383</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Mon, 11 Feb 2008 23:04:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/2008/02/09/scalable-twitter/#comment-33383</guid>
		<description>Sergey,

If you send things to a group of 30 people, or receive them from a group of 50, and you change who those groups are from hour to hour or message to message, where is that filtering going to be enforced?  The UI can work on your Blackberry or iPhone, but will the logic work there too?  I don&#039;t think so; you have to go to a server.  Could that server be your personal choice of &quot;parent&quot; server for your clients? I guess so. I also must confess that there&#039;s an inevitable element of distribution once enterprises start messaging behind their firewalls, yet wanting to connect to the outside world, and I haven&#039;t really thought that aspect through.

But I still think the idea of writing messages to disk before sending them onward is just braindead.  Send them first, THEN persist them quickly, but without allowing that persistence to be a bottleneck.  XMPP doesn&#039;t obviate the need for CEP, any more than CEP would replace XMPP.

CAM</description>
		<content:encoded><![CDATA[<p>Sergey,</p>
<p>If you send things to a group of 30 people, or receive them from a group of 50, and you change who those groups are from hour to hour or message to message, where is that filtering going to be enforced?  The UI can work on your Blackberry or iPhone, but will the logic work there too?  I don&#8217;t think so; you have to go to a server.  Could that server be your personal choice of &#8220;parent&#8221; server for your clients? I guess so. I also must confess that there&#8217;s an inevitable element of distribution once enterprises start messaging behind their firewalls, yet wanting to connect to the outside world, and I haven&#8217;t really thought that aspect through.</p>
<p>But I still think the idea of writing messages to disk before sending them onward is just braindead.  Send them first, THEN persist them quickly, but without allowing that persistence to be a bottleneck.  XMPP doesn&#8217;t obviate the need for CEP, any more than CEP would replace XMPP.</p>
<p>CAM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sergey</title>
		<link>http://www.texttechnologies.com/2008/02/09/scalable-twitter/comment-page-1/#comment-33350</link>
		<dc:creator>Sergey</dc:creator>
		<pubDate>Mon, 11 Feb 2008 18:47:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/2008/02/09/scalable-twitter/#comment-33350</guid>
		<description>Curt, maybe it&#039;s my misunderstanding, but XMPP is more about routing messages than a global bus. With Publish-Subscribe Extensions it already has the core functionality of Twitter. It&#039;s also  proven to be scalable. One can pretty much reimplement Twitter on top of existing infrastructure without any problem. I have to admit that I don&#039;t use Twitter myself, so maybe I&#039;m missing some feature that doesn&#039;t project itself too well onto existing Jabber network?</description>
		<content:encoded><![CDATA[<p>Curt, maybe it&#8217;s my misunderstanding, but XMPP is more about routing messages than a global bus. With Publish-Subscribe Extensions it already has the core functionality of Twitter. It&#8217;s also  proven to be scalable. One can pretty much reimplement Twitter on top of existing infrastructure without any problem. I have to admit that I don&#8217;t use Twitter myself, so maybe I&#8217;m missing some feature that doesn&#8217;t project itself too well onto existing Jabber network?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Text Technologies&#187;Blog Archive &#187; Enterprise Twitter</title>
		<link>http://www.texttechnologies.com/2008/02/09/scalable-twitter/comment-page-1/#comment-33301</link>
		<dc:creator>Text Technologies&#187;Blog Archive &#187; Enterprise Twitter</dc:creator>
		<pubDate>Mon, 11 Feb 2008 11:43:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/2008/02/09/scalable-twitter/#comment-33301</guid>
		<description>[...] long discussion Saturday of how to evolve (or replace) Twitter included a short discussion of what might be called Enterprise Twitter. Dennis Howlett just alerted [...]</description>
		<content:encoded><![CDATA[<p>[...] long discussion Saturday of how to evolve (or replace) Twitter included a short discussion of what might be called Enterprise Twitter. Dennis Howlett just alerted [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.444 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2010-01-25 10:28:08 -->
