<?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: Take a Number</title>
	<atom:link href="http://enthusiasm.cozy.org/archives/2005/05/take-a-number/feed" rel="self" type="application/rss+xml" />
	<link>http://enthusiasm.cozy.org/archives/2005/05/take-a-number</link>
	<description>Ben Hyde</description>
	<lastBuildDate>Tue, 31 Jan 2012 13:18:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ascription is an Anathema to any Enthusiasm &#187; Blog Archive &#187; Take a Number</title>
		<link>http://enthusiasm.cozy.org/archives/2005/05/take-a-number/comment-page-1#comment-561</link>
		<dc:creator>Ascription is an Anathema to any Enthusiasm &#187; Blog Archive &#187; Take a Number</dc:creator>
		<pubDate>Sat, 29 Dec 2007 18:15:02 +0000</pubDate>
		<guid isPermaLink="false">http://enthusiasm.cozy.org/archives/2005/05/take-a-number/#comment-561</guid>
		<description>[...] It is almost possible to do this without changing the existing HTTP spec.  For example you set up a Rube Goldberg device with three servers.  One to hand out numbers, one to queue up users, and finally one that actually provides service.   Say you want to sell concert tickets on a first come first serve basis.  As buyers arrive at your server you redirect them, providing a number, to a second server.  This server has only one purpose in live and that&#8217;s to make them wait.  A HTTP server configured to do that for a huge number of users is a bit odd to set up but it&#8217;s not particularly difficult.  This waiting server finally redirects them to the actual selling server at the appropriate time.  The nice thing about this approach is that it removes the incentive for buyers to attempt to poll as fast as possible. Curious, I&#8217;ve mentioned take a number systems before (includes more amusing picture). [...]</description>
		<content:encoded><![CDATA[<p>[...] It is almost possible to do this without changing the existing HTTP spec.  For example you set up a Rube Goldberg device with three servers.  One to hand out numbers, one to queue up users, and finally one that actually provides service.   Say you want to sell concert tickets on a first come first serve basis.  As buyers arrive at your server you redirect them, providing a number, to a second server.  This server has only one purpose in live and that&#8217;s to make them wait.  A HTTP server configured to do that for a huge number of users is a bit odd to set up but it&#8217;s not particularly difficult.  This waiting server finally redirects them to the actual selling server at the appropriate time.  The nice thing about this approach is that it removes the incentive for buyers to attempt to poll as fast as possible. Curious, I&#8217;ve mentioned take a number systems before (includes more amusing picture). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Hyde</title>
		<link>http://enthusiasm.cozy.org/archives/2005/05/take-a-number/comment-page-1#comment-560</link>
		<dc:creator>Ben Hyde</dc:creator>
		<pubDate>Sat, 21 May 2005 08:59:07 +0000</pubDate>
		<guid isPermaLink="false">http://enthusiasm.cozy.org/archives/2005/05/take-a-number/#comment-560</guid>
		<description>you need to stop using my name, basterd. I am the one and true Ben Hyde. Quit impersonating people that you should not.</description>
		<content:encoded><![CDATA[<p>you need to stop using my name, basterd. I am the one and true Ben Hyde. Quit impersonating people that you should not.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

