<?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: Not so irrelevant 011</title>
	<atom:link href="http://dangerouslyirrelevant.org/2008/09/not-so-irrele-2.html/feed" rel="self" type="application/rss+xml" />
	<link>http://dangerouslyirrelevant.org/2008/09/not-so-irrele-2.html</link>
	<description>Technology, leadership, and the future of schools</description>
	<lastBuildDate>Wed, 08 Feb 2012 23:00:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: John Larkin</title>
		<link>http://dangerouslyirrelevant.org/2008/09/not-so-irrele-2.html/comment-page-1#comment-12053</link>
		<dc:creator>John Larkin</dc:creator>
		<pubDate>Tue, 30 Nov 1999 05:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://annahein.com/2008/09/not-so-irrele-2.html#comment-12053</guid>
		<description>Social networking for babies. Well, my cat has a social network with 59 feline friends, some deceased.
http://www.catster.com/cats/603726
Google his name, Sootie, and he will appear within the first 10 links. Crazy.
Cheers,
John
</description>
		<content:encoded><![CDATA[<p>Social networking for babies. Well, my cat has a social network with 59 feline friends, some deceased.<br />
<a href="http://www.catster.com/cats/603726" rel="nofollow">http://www.catster.com/cats/603726</a><br />
Google his name, Sootie, and he will appear within the first 10 links. Crazy.<br />
Cheers,<br />
John</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://dangerouslyirrelevant.org/2008/09/not-so-irrele-2.html/comment-page-1#comment-12054</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Tue, 30 Nov 1999 05:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://annahein.com/2008/09/not-so-irrele-2.html#comment-12054</guid>
		<description>The $70 PC

Its not all it is cracked up to be. The thin-client system/theory/set-up has been around for years - formally called dummy terminals.

I use to work in a district which was hooked on the idea. The dummy-terminal basically logs-into a server remotely. The server contains the software needed for the client working on the terminal. The server also provides a location for the client to save their data.

It all works great if you have a huge beefed-up server which can handle all the software you want to use (also some software cannot be loaded as a &quot;server based&quot; application) and the number of clients you want to access the software at the same time.

Also some &quot;thin-clients&quot; are much better then others. Some have built in RAM which allow for them to relieve some stress from the server. Some have usb ports, cdroms, even solid state HD space for temporary files.

When it is all said in done I don&#039;t think it really saves you that much. They are a lot more networking work and depending on the software you would like to use - possibly impractical. You would also need to purchase a extremely fast beefed-up server to house all the server side applications.

What do I know though - I am just a shop teacher :)

Tony
</description>
		<content:encoded><![CDATA[<p>The $70 PC</p>
<p>Its not all it is cracked up to be. The thin-client system/theory/set-up has been around for years &#8211; formally called dummy terminals.</p>
<p>I use to work in a district which was hooked on the idea. The dummy-terminal basically logs-into a server remotely. The server contains the software needed for the client working on the terminal. The server also provides a location for the client to save their data.</p>
<p>It all works great if you have a huge beefed-up server which can handle all the software you want to use (also some software cannot be loaded as a &#8220;server based&#8221; application) and the number of clients you want to access the software at the same time.</p>
<p>Also some &#8220;thin-clients&#8221; are much better then others. Some have built in RAM which allow for them to relieve some stress from the server. Some have usb ports, cdroms, even solid state HD space for temporary files.</p>
<p>When it is all said in done I don&#8217;t think it really saves you that much. They are a lot more networking work and depending on the software you would like to use &#8211; possibly impractical. You would also need to purchase a extremely fast beefed-up server to house all the server side applications.</p>
<p>What do I know though &#8211; I am just a shop teacher <img src='http://dangerouslyirrelevant.org/site/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Tony</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Fisch</title>
		<link>http://dangerouslyirrelevant.org/2008/09/not-so-irrele-2.html/comment-page-1#comment-12055</link>
		<dc:creator>Karl Fisch</dc:creator>
		<pubDate>Tue, 30 Nov 1999 05:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://annahein.com/2008/09/not-so-irrele-2.html#comment-12055</guid>
		<description>We&#039;re actually using n-computing in my building/district - with mixed results. They pretty much work as advertised, as long as you only put one n-computing card in a computer (it&#039;s possible to put two, but they get pretty flaky and n-computing isn&#039;t really recommending that just yet - if that would work, the cost savings are even better).

They work fine for basic uses (Word Processing, PowerPoint, web-based stuff), but you don&#039;t want to be doing video editing on them because of the shared resources. Also, some apps won&#039;t work (like Google Earth and some educational apps like TuxType - that can&#039;t run multiple sessions of the software). We still have to pay MS software licensing for 4 machines (host and 3 clients), but only one Symantec license.

Ultimately I don&#039;t see these as a solution because they&#039;re tied (pretty much literally) to desktop machines. But for a short-term solution to provide more access for students, they work fairly well.
</description>
		<content:encoded><![CDATA[<p>We&#8217;re actually using n-computing in my building/district &#8211; with mixed results. They pretty much work as advertised, as long as you only put one n-computing card in a computer (it&#8217;s possible to put two, but they get pretty flaky and n-computing isn&#8217;t really recommending that just yet &#8211; if that would work, the cost savings are even better).</p>
<p>They work fine for basic uses (Word Processing, PowerPoint, web-based stuff), but you don&#8217;t want to be doing video editing on them because of the shared resources. Also, some apps won&#8217;t work (like Google Earth and some educational apps like TuxType &#8211; that can&#8217;t run multiple sessions of the software). We still have to pay MS software licensing for 4 machines (host and 3 clients), but only one Symantec license.</p>
<p>Ultimately I don&#8217;t see these as a solution because they&#8217;re tied (pretty much literally) to desktop machines. But for a short-term solution to provide more access for students, they work fairly well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: drsloomis</title>
		<link>http://dangerouslyirrelevant.org/2008/09/not-so-irrele-2.html/comment-page-1#comment-12056</link>
		<dc:creator>drsloomis</dc:creator>
		<pubDate>Tue, 30 Nov 1999 05:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://annahein.com/2008/09/not-so-irrele-2.html#comment-12056</guid>
		<description>Having had multiple opportunities to work with various sundry thin-client setups over the past 10 years, I gotta agree with Karl on this one...they&#039;re great for things like a word processing lab or the like, but for anything more than basic office functions, the amount of network support needed (such as infrastructure and the beefy server mentioned by Tony) tend to negate whatever savings there may be.

On another topic, I would have characterized Wolman&#039;s WIRED article more as snarky and dismissive rather than quick and effective. Whether I agree with the positions or not, some of the works he brushes aside with a condescending wave of his hand actually raise some valid questions that we as educators should allow to be part of the discussion. The kind of smug dismissal prevalent in Wolman&#039;s prose only serves to close down the very discussion we should be encouraging--though WIRED&#039;s readership would certainly qualify as the choir.
</description>
		<content:encoded><![CDATA[<p>Having had multiple opportunities to work with various sundry thin-client setups over the past 10 years, I gotta agree with Karl on this one&#8230;they&#8217;re great for things like a word processing lab or the like, but for anything more than basic office functions, the amount of network support needed (such as infrastructure and the beefy server mentioned by Tony) tend to negate whatever savings there may be.</p>
<p>On another topic, I would have characterized Wolman&#8217;s WIRED article more as snarky and dismissive rather than quick and effective. Whether I agree with the positions or not, some of the works he brushes aside with a condescending wave of his hand actually raise some valid questions that we as educators should allow to be part of the discussion. The kind of smug dismissal prevalent in Wolman&#8217;s prose only serves to close down the very discussion we should be encouraging&#8211;though WIRED&#8217;s readership would certainly qualify as the choir.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

