<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_12_11_1339249</id>
	<title>Red Hat Open Sources SPICE Desktop Virtualization</title>
	<author>kdawson</author>
	<datestamp>1260542040000</datestamp>
	<htmltext>laxl writes <i>"Linux vendor Red Hat has <a href="http://www.techworld.com.au/article/329382/red\_hat\_open\_sources\_desktop\_application\_protocol">open sourced the Simple Protocol for Independent Computing Environment (SPICE)</a> virtual desktop protocol it acquired last year with Qumranet, which used SPICE for its own commercial desktop-virtualization product, called SolidIce. SPICE can be used to deploy virtual desktops from a server out to remote computers, such as desktop PCs and thin-client devices. It is similar to other rendering protocols used for remote desktop management such as Microsoft's Remote Desktop Protocol or Citrix's Independent Computing Architecture. SPICE supports rendering virtual instances of Windows XP and Windows 7, as well as Red Hat Enterprise Linux. According to Red Hat, SPICE has advantages over other protocols in that it can dynamically customize desktop instances to fit specific operating environments. According to the article, most of the SPICE code is available under the GNU GPLv2, though parts are also licensed under LGPL- and BSD-styled licenses."</i></htmltext>
<tokenext>laxl writes " Linux vendor Red Hat has open sourced the Simple Protocol for Independent Computing Environment ( SPICE ) virtual desktop protocol it acquired last year with Qumranet , which used SPICE for its own commercial desktop-virtualization product , called SolidIce .
SPICE can be used to deploy virtual desktops from a server out to remote computers , such as desktop PCs and thin-client devices .
It is similar to other rendering protocols used for remote desktop management such as Microsoft 's Remote Desktop Protocol or Citrix 's Independent Computing Architecture .
SPICE supports rendering virtual instances of Windows XP and Windows 7 , as well as Red Hat Enterprise Linux .
According to Red Hat , SPICE has advantages over other protocols in that it can dynamically customize desktop instances to fit specific operating environments .
According to the article , most of the SPICE code is available under the GNU GPLv2 , though parts are also licensed under LGPL- and BSD-styled licenses .
"</tokentext>
<sentencetext>laxl writes "Linux vendor Red Hat has open sourced the Simple Protocol for Independent Computing Environment (SPICE) virtual desktop protocol it acquired last year with Qumranet, which used SPICE for its own commercial desktop-virtualization product, called SolidIce.
SPICE can be used to deploy virtual desktops from a server out to remote computers, such as desktop PCs and thin-client devices.
It is similar to other rendering protocols used for remote desktop management such as Microsoft's Remote Desktop Protocol or Citrix's Independent Computing Architecture.
SPICE supports rendering virtual instances of Windows XP and Windows 7, as well as Red Hat Enterprise Linux.
According to Red Hat, SPICE has advantages over other protocols in that it can dynamically customize desktop instances to fit specific operating environments.
According to the article, most of the SPICE code is available under the GNU GPLv2, though parts are also licensed under LGPL- and BSD-styled licenses.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401604</id>
	<title>VDI here we come</title>
	<author>Anonymous</author>
	<datestamp>1260546300000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>This really solves the last remaining hurdle for VDI thin client vertical engineering domain.

Going to grab the git source tonight and test it out.

Would be cool if an in browser NSAPI based plugin architecture was built on this.
Run your thin clients on Google OS ( or something else), and then you can run all your legacy fat clients on your virtual servers and your uses just access them through a browser.

I noticed that people have even worked on Javascript level RDP and No-machine client implementations. Obviously a bit slow for real world.

Anyone know if KVM has dedicated VDI infrastructure servers yet ?
Ged</htmltext>
<tokenext>This really solves the last remaining hurdle for VDI thin client vertical engineering domain .
Going to grab the git source tonight and test it out .
Would be cool if an in browser NSAPI based plugin architecture was built on this .
Run your thin clients on Google OS ( or something else ) , and then you can run all your legacy fat clients on your virtual servers and your uses just access them through a browser .
I noticed that people have even worked on Javascript level RDP and No-machine client implementations .
Obviously a bit slow for real world .
Anyone know if KVM has dedicated VDI infrastructure servers yet ?
Ged</tokentext>
<sentencetext>This really solves the last remaining hurdle for VDI thin client vertical engineering domain.
Going to grab the git source tonight and test it out.
Would be cool if an in browser NSAPI based plugin architecture was built on this.
Run your thin clients on Google OS ( or something else), and then you can run all your legacy fat clients on your virtual servers and your uses just access them through a browser.
I noticed that people have even worked on Javascript level RDP and No-machine client implementations.
Obviously a bit slow for real world.
Anyone know if KVM has dedicated VDI infrastructure servers yet ?
Ged</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402338</id>
	<title>So what the FUCK does it do?</title>
	<author>Anonymous</author>
	<datestamp>1260549660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I've seen a dozen blog posts in my reader about this, and I have been unable to far to figure out WTF that thing is supposed to do. Is it a remote display protocol? If so, how does it differ from RDP or NX?</p></htmltext>
<tokenext>I 've seen a dozen blog posts in my reader about this , and I have been unable to far to figure out WTF that thing is supposed to do .
Is it a remote display protocol ?
If so , how does it differ from RDP or NX ?</tokentext>
<sentencetext>I've seen a dozen blog posts in my reader about this, and I have been unable to far to figure out WTF that thing is supposed to do.
Is it a remote display protocol?
If so, how does it differ from RDP or NX?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401742</id>
	<title>Re:Stop overloading common tech acronyms!</title>
	<author>Anonymous</author>
	<datestamp>1260547020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I too thought the same thing. My immediate reaction was, "isn't SPICE already open?" I also got quite excited about the implications of SPICE in the title. Albeit, not the SPICE that I am all too familiar with.</p></htmltext>
<tokenext>I too thought the same thing .
My immediate reaction was , " is n't SPICE already open ?
" I also got quite excited about the implications of SPICE in the title .
Albeit , not the SPICE that I am all too familiar with .</tokentext>
<sentencetext>I too thought the same thing.
My immediate reaction was, "isn't SPICE already open?
" I also got quite excited about the implications of SPICE in the title.
Albeit, not the SPICE that I am all too familiar with.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401942</id>
	<title>Re:Dune</title>
	<author>jollyreaper</author>
	<datestamp>1260547980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I wonder what the CHOAM will think about this?</p></div><p>Better ask Paul. (see sig)</p></div>
	</htmltext>
<tokenext>I wonder what the CHOAM will think about this ? Better ask Paul .
( see sig )</tokentext>
<sentencetext>I wonder what the CHOAM will think about this?Better ask Paul.
(see sig)
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401500</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30404474</id>
	<title>SPICE?</title>
	<author>EQ</author>
	<datestamp>1260557880000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>If the plural of mouse is mice, shouldn't the plural of spouse be spice?<nobr> <wbr></nobr>/pinky</htmltext>
<tokenext>If the plural of mouse is mice , should n't the plural of spouse be spice ?
/pinky</tokentext>
<sentencetext>If the plural of mouse is mice, shouldn't the plural of spouse be spice?
/pinky</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30403522</id>
	<title>Why SPICE is useful</title>
	<author>Anonymous</author>
	<datestamp>1260554280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>It's for people who can't spell VNC.</p></htmltext>
<tokenext>It 's for people who ca n't spell VNC .</tokentext>
<sentencetext>It's for people who can't spell VNC.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30404314</id>
	<title>Red Hat == "GOOD GUYS!"</title>
	<author>mcrbids</author>
	<datestamp>1260557100000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>This is yet another example of too many to name, of Red Hat being an all-around bunch of warm and fuzzy penguins, guys! And this is so typical of them: buy a proprietary product, and as soon as they decide to do something with it, they open source it first!</p><p>RedHat has NEVER deviated from their policy of releasing SRPMS for all their stuff. You can very literally roll your own distro simply by taking their SRPM and compiling them! And a number of groups have done just that: <a href="http://whiteboxlinux.org/" title="whiteboxlinux.org">White Box Linux</a> [whiteboxlinux.org], <a href="http://www.centos.org/" title="centos.org">CentOS</a> [centos.org] and <a href="https://www.scientificlinux.org/" title="scientificlinux.org">Scientific Linux</a> [scientificlinux.org].</p><p>Red Hat employs some of the most prolific contributors to the Linux Kernel and is a vital force in making Linux what it is today. Go Red Hat!</p><p>PS: No, I don't work for them, just a very happy customer!</p></htmltext>
<tokenext>This is yet another example of too many to name , of Red Hat being an all-around bunch of warm and fuzzy penguins , guys !
And this is so typical of them : buy a proprietary product , and as soon as they decide to do something with it , they open source it first ! RedHat has NEVER deviated from their policy of releasing SRPMS for all their stuff .
You can very literally roll your own distro simply by taking their SRPM and compiling them !
And a number of groups have done just that : White Box Linux [ whiteboxlinux.org ] , CentOS [ centos.org ] and Scientific Linux [ scientificlinux.org ] .Red Hat employs some of the most prolific contributors to the Linux Kernel and is a vital force in making Linux what it is today .
Go Red Hat ! PS : No , I do n't work for them , just a very happy customer !</tokentext>
<sentencetext>This is yet another example of too many to name, of Red Hat being an all-around bunch of warm and fuzzy penguins, guys!
And this is so typical of them: buy a proprietary product, and as soon as they decide to do something with it, they open source it first!RedHat has NEVER deviated from their policy of releasing SRPMS for all their stuff.
You can very literally roll your own distro simply by taking their SRPM and compiling them!
And a number of groups have done just that: White Box Linux [whiteboxlinux.org], CentOS [centos.org] and Scientific Linux [scientificlinux.org].Red Hat employs some of the most prolific contributors to the Linux Kernel and is a vital force in making Linux what it is today.
Go Red Hat!PS: No, I don't work for them, just a very happy customer!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402256</id>
	<title>Re:Stop overloading common tech acronyms!</title>
	<author>bperkins</author>
	<datestamp>1260549240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I agree that it's annoying, though in my experience people never refer to SPICE without prefacing it with "Berkeley".  SPICE all by itself is used as a generic term.</p><p>TFA could also use some more references.  It sounds intriguing, but I've been around long enough to be distrustful of what's in press releases.</p></htmltext>
<tokenext>I agree that it 's annoying , though in my experience people never refer to SPICE without prefacing it with " Berkeley " .
SPICE all by itself is used as a generic term.TFA could also use some more references .
It sounds intriguing , but I 've been around long enough to be distrustful of what 's in press releases .</tokentext>
<sentencetext>I agree that it's annoying, though in my experience people never refer to SPICE without prefacing it with "Berkeley".
SPICE all by itself is used as a generic term.TFA could also use some more references.
It sounds intriguing, but I've been around long enough to be distrustful of what's in press releases.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30404954</id>
	<title>Re:Platform independence depends on implementation</title>
	<author>caseih</author>
	<datestamp>1260559920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>VNC is definitely not in the same league as SPICE.  SPICE more directly compares with and competes with Citrix and MS Terminal Server.  It not only ports the display, it can port individual apps, connects drives and printers, and is capable of doing fancy graphical things like movie playback in a way that's much more optimal and efficient than VNC can do.  SPICE might compare in some measure to NX, but NX is really about optimizing an X11 command stream, which is only an X11 thing, so it's of more limited use than what SPICE is intended to be.</p><p>Whether SPICE turns out to be anything useful to the community at large, as NX has become, I don't know.</p></htmltext>
<tokenext>VNC is definitely not in the same league as SPICE .
SPICE more directly compares with and competes with Citrix and MS Terminal Server .
It not only ports the display , it can port individual apps , connects drives and printers , and is capable of doing fancy graphical things like movie playback in a way that 's much more optimal and efficient than VNC can do .
SPICE might compare in some measure to NX , but NX is really about optimizing an X11 command stream , which is only an X11 thing , so it 's of more limited use than what SPICE is intended to be.Whether SPICE turns out to be anything useful to the community at large , as NX has become , I do n't know .</tokentext>
<sentencetext>VNC is definitely not in the same league as SPICE.
SPICE more directly compares with and competes with Citrix and MS Terminal Server.
It not only ports the display, it can port individual apps, connects drives and printers, and is capable of doing fancy graphical things like movie playback in a way that's much more optimal and efficient than VNC can do.
SPICE might compare in some measure to NX, but NX is really about optimizing an X11 command stream, which is only an X11 thing, so it's of more limited use than what SPICE is intended to be.Whether SPICE turns out to be anything useful to the community at large, as NX has become, I don't know.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402540</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30404332</id>
	<title>Re:Stop overloading common tech acronyms!</title>
	<author>Creepy</author>
	<datestamp>1260557160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>exactly my first thought... you'd think there would be some originality with FLAs* that you can't really get with TLAs*@...</p><p>* Five Letter Acronyms<br>*@ Three Letter Acronyms</p></htmltext>
<tokenext>exactly my first thought... you 'd think there would be some originality with FLAs * that you ca n't really get with TLAs * @ ... * Five Letter Acronyms * @ Three Letter Acronyms</tokentext>
<sentencetext>exactly my first thought... you'd think there would be some originality with FLAs* that you can't really get with TLAs*@...* Five Letter Acronyms*@ Three Letter Acronyms</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401870</id>
	<title>Re:SPICE is a circuit simulator</title>
	<author>Anonymous</author>
	<datestamp>1260547560000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>Because it does not matter as both programs are not related at all?<br>
I don't know the fuss about it, I am a IT professional, did some exercises with SPICE (circuit) while in the university and now SPICE (VM) may be interesting for my job as sysadmin. As a sysadmin, I do not need to design circuits anymore, so I don't think I will be ever confused.<br>
<br>
Of course, my apologies if your post was just a joke...</htmltext>
<tokenext>Because it does not matter as both programs are not related at all ?
I do n't know the fuss about it , I am a IT professional , did some exercises with SPICE ( circuit ) while in the university and now SPICE ( VM ) may be interesting for my job as sysadmin .
As a sysadmin , I do not need to design circuits anymore , so I do n't think I will be ever confused .
Of course , my apologies if your post was just a joke.. .</tokentext>
<sentencetext>Because it does not matter as both programs are not related at all?
I don't know the fuss about it, I am a IT professional, did some exercises with SPICE (circuit) while in the university and now SPICE (VM) may be interesting for my job as sysadmin.
As a sysadmin, I do not need to design circuits anymore, so I don't think I will be ever confused.
Of course, my apologies if your post was just a joke...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401608</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401556</id>
	<title>But how many</title>
	<author>Icegryphon</author>
	<datestamp>1260546120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>How many thinclients/hosts support the protocol to connect to it?<br>
Isn't this different from RDP or ICA which are pretty much supported everywhere?</htmltext>
<tokenext>How many thinclients/hosts support the protocol to connect to it ?
Is n't this different from RDP or ICA which are pretty much supported everywhere ?</tokentext>
<sentencetext>How many thinclients/hosts support the protocol to connect to it?
Isn't this different from RDP or ICA which are pretty much supported everywhere?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402442</id>
	<title>Re:Stop overloading common tech acronyms!</title>
	<author>Anonymous</author>
	<datestamp>1260550200000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>nobody calls "OS X" "X".</htmltext>
<tokenext>nobody calls " OS X " " X " .</tokentext>
<sentencetext>nobody calls "OS X" "X".</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402488</id>
	<title>Re:Stop overloading common tech acronyms!</title>
	<author>Lord Bitman</author>
	<datestamp>1260550380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>no, SPICE is someone's idea of a clever attempt at manufacturing a cool-sounding acronym based on an extremely short and common word (the only one that's shorter and more common might be ICE, which this is derived from).<br>No one can claim ownership on such a stupid, short, generic acronym. There are at least 20,000 meanings of "ICE", and adding "SP" on the front does not make you special or original. They're both lame, get over it.</p><p>This is not nearly as bad as Microsoft calling its product "Windows", or Google calling its javascript library "Closure".</p></htmltext>
<tokenext>no , SPICE is someone 's idea of a clever attempt at manufacturing a cool-sounding acronym based on an extremely short and common word ( the only one that 's shorter and more common might be ICE , which this is derived from ) .No one can claim ownership on such a stupid , short , generic acronym .
There are at least 20,000 meanings of " ICE " , and adding " SP " on the front does not make you special or original .
They 're both lame , get over it.This is not nearly as bad as Microsoft calling its product " Windows " , or Google calling its javascript library " Closure " .</tokentext>
<sentencetext>no, SPICE is someone's idea of a clever attempt at manufacturing a cool-sounding acronym based on an extremely short and common word (the only one that's shorter and more common might be ICE, which this is derived from).No one can claim ownership on such a stupid, short, generic acronym.
There are at least 20,000 meanings of "ICE", and adding "SP" on the front does not make you special or original.
They're both lame, get over it.This is not nearly as bad as Microsoft calling its product "Windows", or Google calling its javascript library "Closure".</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402540</id>
	<title>Platform independence depends on implementation</title>
	<author>cerberusss</author>
	<datestamp>1260550620000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>From the summary:</p><blockquote><div><p>Simple Protocol for <b>Independent Computing</b> Environment (SPICE)  supports rendering virtual instances of Windows XP and Windows 7, as well as Red Hat Enterprise Linux</p></div></blockquote><p>(Emphasis mine). Aha, so it's platform independent? And they support... Two! *badum-ching* operating systems: Windows and Linux. Compare that to VNC, of which it is hard to find an OS that doesn't support it.</p></div>
	</htmltext>
<tokenext>From the summary : Simple Protocol for Independent Computing Environment ( SPICE ) supports rendering virtual instances of Windows XP and Windows 7 , as well as Red Hat Enterprise Linux ( Emphasis mine ) .
Aha , so it 's platform independent ?
And they support... Two ! * badum-ching * operating systems : Windows and Linux .
Compare that to VNC , of which it is hard to find an OS that does n't support it .</tokentext>
<sentencetext>From the summary:Simple Protocol for Independent Computing Environment (SPICE)  supports rendering virtual instances of Windows XP and Windows 7, as well as Red Hat Enterprise Linux(Emphasis mine).
Aha, so it's platform independent?
And they support... Two! *badum-ching* operating systems: Windows and Linux.
Compare that to VNC, of which it is hard to find an OS that doesn't support it.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401500</id>
	<title>Dune</title>
	<author>Anonymous</author>
	<datestamp>1260545880000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>I wonder what the CHOAM will think about this?</htmltext>
<tokenext>I wonder what the CHOAM will think about this ?</tokentext>
<sentencetext>I wonder what the CHOAM will think about this?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30406138</id>
	<title>Re:Stop overloading common tech acronyms!</title>
	<author>ThinkingGuy</author>
	<datestamp>1260522360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I've seen worse. How about...<br>
RMS = <a href="http://stallman.org/" title="stallman.org" rel="nofollow">Richard Stallman</a> [stallman.org] - Mister Free Software himself
<br>
RMS = Windows <a href="http://en.wikipedia.org/wiki/Rights\_Management\_Services" title="wikipedia.org" rel="nofollow">Rights Management Services</a> [wikipedia.org] - Microsoft's proprietary system for restricting access to documents</htmltext>
<tokenext>I 've seen worse .
How about.. . RMS = Richard Stallman [ stallman.org ] - Mister Free Software himself RMS = Windows Rights Management Services [ wikipedia.org ] - Microsoft 's proprietary system for restricting access to documents</tokentext>
<sentencetext>I've seen worse.
How about...
RMS = Richard Stallman [stallman.org] - Mister Free Software himself

RMS = Windows Rights Management Services [wikipedia.org] - Microsoft's proprietary system for restricting access to documents</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402562</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401770</id>
	<title>Re:SPICE is a circuit simulator</title>
	<author>jo42</author>
	<datestamp>1260547080000</datestamp>
	<modclass>Troll</modclass>
	<modscore>1</modscore>
	<htmltext><p>Arrogance? Ignorance? Pick one.</p></htmltext>
<tokenext>Arrogance ?
Ignorance ? Pick one .</tokentext>
<sentencetext>Arrogance?
Ignorance? Pick one.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401608</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30501802</id>
	<title>Brian Madden's test results for ICA, RDP, SPICE</title>
	<author>bmullan</author>
	<datestamp>1261236180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Saw Brian Madden's video's recently with the results of their testing/comparison of ICA, RDP, SPICE

see:
<a href="http://media.brianmadden.com/qumranetvids/blogplayerstatic.asp" title="brianmadden.com" rel="nofollow">http://media.brianmadden.com/qumranetvids/blogplayerstatic.asp</a> [brianmadden.com]

It was very clear that SPICE far outperformed either ICA or RDP.</htmltext>
<tokenext>Saw Brian Madden 's video 's recently with the results of their testing/comparison of ICA , RDP , SPICE see : http : //media.brianmadden.com/qumranetvids/blogplayerstatic.asp [ brianmadden.com ] It was very clear that SPICE far outperformed either ICA or RDP .</tokentext>
<sentencetext>Saw Brian Madden's video's recently with the results of their testing/comparison of ICA, RDP, SPICE

see:
http://media.brianmadden.com/qumranetvids/blogplayerstatic.asp [brianmadden.com]

It was very clear that SPICE far outperformed either ICA or RDP.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30403734</id>
	<title>Re:Stop overloading common tech acronyms!</title>
	<author>Anonymous</author>
	<datestamp>1260555000000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>It would be nice if this tehcnology is coupled with the new " Protocol of Enhanced Network Information and Security ".   SPICE/PENIS ftw !</p></htmltext>
<tokenext>It would be nice if this tehcnology is coupled with the new " Protocol of Enhanced Network Information and Security " .
SPICE/PENIS ftw !</tokentext>
<sentencetext>It would be nice if this tehcnology is coupled with the new " Protocol of Enhanced Network Information and Security ".
SPICE/PENIS ftw !</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402562</id>
	<title>Re:Stop overloading common tech acronyms!</title>
	<author>Anonymous</author>
	<datestamp>1260550680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I have yet to see worse than overloading IP to mean both "Internet Protocol" and "Intellectual Property". Now <em>that's</em> confusing.</p><p>
&nbsp; &nbsp; &nbsp; --- Mr. DOS</p></htmltext>
<tokenext>I have yet to see worse than overloading IP to mean both " Internet Protocol " and " Intellectual Property " .
Now that 's confusing .
      --- Mr. DOS</tokentext>
<sentencetext>I have yet to see worse than overloading IP to mean both "Internet Protocol" and "Intellectual Property".
Now that's confusing.
      --- Mr. DOS</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401636</id>
	<title>Re:SPICE is a circuit simulator</title>
	<author>Anonymous</author>
	<datestamp>1260546480000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Additionally, SPICE (circuit simulator) is already open source.</p><p>I came here thinking what the heck is Red Hat doing open sourcing an open source program?</p></htmltext>
<tokenext>Additionally , SPICE ( circuit simulator ) is already open source.I came here thinking what the heck is Red Hat doing open sourcing an open source program ?</tokentext>
<sentencetext>Additionally, SPICE (circuit simulator) is already open source.I came here thinking what the heck is Red Hat doing open sourcing an open source program?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401608</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401644</id>
	<title>BUT DOES IS ACCELERATE DX (video) BUFFERS ??</title>
	<author>Anonymous</author>
	<datestamp>1260546480000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>If not, go home.  We don't need yet another "hero".</p></htmltext>
<tokenext>If not , go home .
We do n't need yet another " hero " .</tokentext>
<sentencetext>If not, go home.
We don't need yet another "hero".</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544</id>
	<title>Stop overloading common tech acronyms!</title>
	<author>Octorian</author>
	<datestamp>1260546060000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>Seriously, SPICE stands for "Simulation Program with Integrated Circuit Emphasis" and is a circuit simulator.</p><p>(If this was a couple years ago, I'd rant that UML stands for "Unified Modeling Language" (not User-Mode-Linux), or that X stands for "X Window System" (Not MacOS 10))</p></htmltext>
<tokenext>Seriously , SPICE stands for " Simulation Program with Integrated Circuit Emphasis " and is a circuit simulator .
( If this was a couple years ago , I 'd rant that UML stands for " Unified Modeling Language " ( not User-Mode-Linux ) , or that X stands for " X Window System " ( Not MacOS 10 ) )</tokentext>
<sentencetext>Seriously, SPICE stands for "Simulation Program with Integrated Circuit Emphasis" and is a circuit simulator.
(If this was a couple years ago, I'd rant that UML stands for "Unified Modeling Language" (not User-Mode-Linux), or that X stands for "X Window System" (Not MacOS 10))</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30404638</id>
	<title>The VDI Protocol Wars</title>
	<author>Natales</author>
	<datestamp>1260558600000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>This is not a bad thing. For years, the only alternatives for virtual desktops were either proprietary (ICA comes to mind) or OS-dependent (Sun ALP, MSFT RDP, X, NX), leaving VNC as the only OS-independent option. VNC was (and still is) great, but let's face it, it was never intended to be used for real massive VDI-type deployments, even over the WAN. SPICE is supposed to have a good LAN performance, but still doesn't quite cut it for long latencies over the WAN. May be with this move, SPICE can be improved to also address those use cases.</p><p>For now, the most advanced thing I've seen is Teradici's PCoIP protocol that works really well in any environment, and they licensed it to VMware to be used in the new View 4 product line as a pure software implementation (as a disclaimer, I work for VMware, but PCoIP blew my mind way before we did anything with them).</p><p>In any case, 2010 is shaping to be the year of the virtual desktop, and competition is a good thing!</p></htmltext>
<tokenext>This is not a bad thing .
For years , the only alternatives for virtual desktops were either proprietary ( ICA comes to mind ) or OS-dependent ( Sun ALP , MSFT RDP , X , NX ) , leaving VNC as the only OS-independent option .
VNC was ( and still is ) great , but let 's face it , it was never intended to be used for real massive VDI-type deployments , even over the WAN .
SPICE is supposed to have a good LAN performance , but still does n't quite cut it for long latencies over the WAN .
May be with this move , SPICE can be improved to also address those use cases.For now , the most advanced thing I 've seen is Teradici 's PCoIP protocol that works really well in any environment , and they licensed it to VMware to be used in the new View 4 product line as a pure software implementation ( as a disclaimer , I work for VMware , but PCoIP blew my mind way before we did anything with them ) .In any case , 2010 is shaping to be the year of the virtual desktop , and competition is a good thing !</tokentext>
<sentencetext>This is not a bad thing.
For years, the only alternatives for virtual desktops were either proprietary (ICA comes to mind) or OS-dependent (Sun ALP, MSFT RDP, X, NX), leaving VNC as the only OS-independent option.
VNC was (and still is) great, but let's face it, it was never intended to be used for real massive VDI-type deployments, even over the WAN.
SPICE is supposed to have a good LAN performance, but still doesn't quite cut it for long latencies over the WAN.
May be with this move, SPICE can be improved to also address those use cases.For now, the most advanced thing I've seen is Teradici's PCoIP protocol that works really well in any environment, and they licensed it to VMware to be used in the new View 4 product line as a pure software implementation (as a disclaimer, I work for VMware, but PCoIP blew my mind way before we did anything with them).In any case, 2010 is shaping to be the year of the virtual desktop, and competition is a good thing!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30405190</id>
	<title>Spice maintainer on qemu list</title>
	<author>Anonymous</author>
	<datestamp>1260560820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>The primary Spice developer appears to be making a complete fool of himself on the qemu mailing list:</p><p>http://lists.nongnu.org/archive/html/qemu-devel/2009-12/msg01182.html</p></htmltext>
<tokenext>The primary Spice developer appears to be making a complete fool of himself on the qemu mailing list : http : //lists.nongnu.org/archive/html/qemu-devel/2009-12/msg01182.html</tokentext>
<sentencetext>The primary Spice developer appears to be making a complete fool of himself on the qemu mailing list:http://lists.nongnu.org/archive/html/qemu-devel/2009-12/msg01182.html</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402364</id>
	<title>Re:Stop overloading common tech acronyms!</title>
	<author>Speare</author>
	<datestamp>1260549720000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext>Yeah, and while we're at it, NASA:  "Orion" means exploding nukes under a blast plate, not providing a cushy crew cabin.<nobr> <wbr></nobr>:)</htmltext>
<tokenext>Yeah , and while we 're at it , NASA : " Orion " means exploding nukes under a blast plate , not providing a cushy crew cabin .
: )</tokentext>
<sentencetext>Yeah, and while we're at it, NASA:  "Orion" means exploding nukes under a blast plate, not providing a cushy crew cabin.
:)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30405218</id>
	<title>I'd rather they fixed Windows guest support</title>
	<author>melted</author>
	<datestamp>1260560940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'd rather they fixed Windows guest support. I've tried it (in Ubuntu Karmic), and it's horrible if you want to run Windows in it (both XP and Win7). Very slow, timer lags behind, network and disk throughput are super slow even with virtio guest drivers. Linux runs fine as a guest on the same box.</p><p>I guess it's unfair to \_demand\_ anything if something cost you zero dollars (gifted horse thing and all), but VMWare ESX and HyperV Server also cost zero dollars these days, and they both run Windows just fine.</p></htmltext>
<tokenext>I 'd rather they fixed Windows guest support .
I 've tried it ( in Ubuntu Karmic ) , and it 's horrible if you want to run Windows in it ( both XP and Win7 ) .
Very slow , timer lags behind , network and disk throughput are super slow even with virtio guest drivers .
Linux runs fine as a guest on the same box.I guess it 's unfair to \ _demand \ _ anything if something cost you zero dollars ( gifted horse thing and all ) , but VMWare ESX and HyperV Server also cost zero dollars these days , and they both run Windows just fine .</tokentext>
<sentencetext>I'd rather they fixed Windows guest support.
I've tried it (in Ubuntu Karmic), and it's horrible if you want to run Windows in it (both XP and Win7).
Very slow, timer lags behind, network and disk throughput are super slow even with virtio guest drivers.
Linux runs fine as a guest on the same box.I guess it's unfair to \_demand\_ anything if something cost you zero dollars (gifted horse thing and all), but VMWare ESX and HyperV Server also cost zero dollars these days, and they both run Windows just fine.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401976</id>
	<title>Re:Stop overloading common tech acronyms!</title>
	<author>Anonymous</author>
	<datestamp>1260548100000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><p>So, would this be a bad time to introduce my newly designed thin-client PC called the "Generic Network Unit" (GNU) and my new programming language for thin client computer graphics, the "GNU Graphics Programming Language" (GNU GPL)?</p></htmltext>
<tokenext>So , would this be a bad time to introduce my newly designed thin-client PC called the " Generic Network Unit " ( GNU ) and my new programming language for thin client computer graphics , the " GNU Graphics Programming Language " ( GNU GPL ) ?</tokentext>
<sentencetext>So, would this be a bad time to introduce my newly designed thin-client PC called the "Generic Network Unit" (GNU) and my new programming language for thin client computer graphics, the "GNU Graphics Programming Language" (GNU GPL)?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401608</id>
	<title>SPICE is a circuit simulator</title>
	<author>Anonymous</author>
	<datestamp>1260546360000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>Why would they take the name of an existing well-known software program?</p></htmltext>
<tokenext>Why would they take the name of an existing well-known software program ?</tokentext>
<sentencetext>Why would they take the name of an existing well-known software program?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30403362</id>
	<title>Re:So what the FUCK does it do?</title>
	<author>AlXtreme</author>
	<datestamp>1260553800000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><blockquote><div><p>Is it a remote display protocol? If so, how does it differ from RDP or NX?</p></div></blockquote><p>It's more Citrix than RDP or NX. You have a Linux server with multiple qemu/kvm instances, each of which are accessed from a client (Linux/Windows).</p><p>The advantage is that you can have multiple clients on a single server, push CPU/GPU-intensive display operations to the client and have access to client-side hardware from within the virtualized server instance.</p><p>Normally I'd add a RTFA-sneer, but I read through the site and am only moderately sure I got the above correct. Should be very useful for large-scale Linux desktop deployments however: server-side maintenance with client-side display speed &amp; hardware support. In theory.</p></div>
	</htmltext>
<tokenext>Is it a remote display protocol ?
If so , how does it differ from RDP or NX ? It 's more Citrix than RDP or NX .
You have a Linux server with multiple qemu/kvm instances , each of which are accessed from a client ( Linux/Windows ) .The advantage is that you can have multiple clients on a single server , push CPU/GPU-intensive display operations to the client and have access to client-side hardware from within the virtualized server instance.Normally I 'd add a RTFA-sneer , but I read through the site and am only moderately sure I got the above correct .
Should be very useful for large-scale Linux desktop deployments however : server-side maintenance with client-side display speed &amp; hardware support .
In theory .</tokentext>
<sentencetext>Is it a remote display protocol?
If so, how does it differ from RDP or NX?It's more Citrix than RDP or NX.
You have a Linux server with multiple qemu/kvm instances, each of which are accessed from a client (Linux/Windows).The advantage is that you can have multiple clients on a single server, push CPU/GPU-intensive display operations to the client and have access to client-side hardware from within the virtualized server instance.Normally I'd add a RTFA-sneer, but I read through the site and am only moderately sure I got the above correct.
Should be very useful for large-scale Linux desktop deployments however: server-side maintenance with client-side display speed &amp; hardware support.
In theory.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402338</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402402</id>
	<title>Re:Stop overloading common tech acronyms!</title>
	<author>oldhack</author>
	<datestamp>1260549900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Tru dat.  This forces me to boycott Red Hat from now on.</htmltext>
<tokenext>Tru dat .
This forces me to boycott Red Hat from now on .</tokentext>
<sentencetext>Tru dat.
This forces me to boycott Red Hat from now on.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401610</id>
	<title>Multi monitor support</title>
	<author>Anonymous</author>
	<datestamp>1260546360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Hoping for remote multi monitor support or I'm stuck with X terminals over ssh.</p></htmltext>
<tokenext>Hoping for remote multi monitor support or I 'm stuck with X terminals over ssh .</tokentext>
<sentencetext>Hoping for remote multi monitor support or I'm stuck with X terminals over ssh.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30408104</id>
	<title>Re:So what the FUCK does it do?</title>
	<author>gedw99</author>
	<datestamp>1260532620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The difference is HUGE. They are able to export the opengl command to the client or not to the client.

so its not just compressed jpegs like all the others.

google virtualGL as this did it too.

G</htmltext>
<tokenext>The difference is HUGE .
They are able to export the opengl command to the client or not to the client .
so its not just compressed jpegs like all the others .
google virtualGL as this did it too .
G</tokentext>
<sentencetext>The difference is HUGE.
They are able to export the opengl command to the client or not to the client.
so its not just compressed jpegs like all the others.
google virtualGL as this did it too.
G</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402338</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30412172</id>
	<title>Re:The VDI Protocol Wars</title>
	<author>Macka</author>
	<datestamp>1260612900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p> SPICE is supposed to have a good LAN performance, but still doesn't quite cut it for long latencies over the WAN</p></div> </blockquote><p>Can you back up that statement with something solid, or are you just being a nice VMware employee and FUDing the competition before it gets chance to eat your lunch?</p></div>
	</htmltext>
<tokenext>SPICE is supposed to have a good LAN performance , but still does n't quite cut it for long latencies over the WAN Can you back up that statement with something solid , or are you just being a nice VMware employee and FUDing the competition before it gets chance to eat your lunch ?</tokentext>
<sentencetext> SPICE is supposed to have a good LAN performance, but still doesn't quite cut it for long latencies over the WAN Can you back up that statement with something solid, or are you just being a nice VMware employee and FUDing the competition before it gets chance to eat your lunch?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30404638</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401998</id>
	<title>Re:Stop overloading common tech acronyms!</title>
	<author>MobyDisk</author>
	<datestamp>1260548160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This was the first thing I thought of too.</p></htmltext>
<tokenext>This was the first thing I thought of too .</tokentext>
<sentencetext>This was the first thing I thought of too.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30403016</id>
	<title>Re:SPICE is a circuit simulator</title>
	<author>Hatta</author>
	<datestamp>1260552420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Oh, in a month they'll change it to FireSPICE.</p></htmltext>
<tokenext>Oh , in a month they 'll change it to FireSPICE .</tokentext>
<sentencetext>Oh, in a month they'll change it to FireSPICE.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401608</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30403264</id>
	<title>acronyms and abbreviations</title>
	<author>mollog</author>
	<datestamp>1260553320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Pedantic, I know, but it's a pet peeve with me.<br> <br>

Although SPICE could be a legitimate acronym, neither UML nor X would be acronyms, they would be abbreviations.<br> <br>

Examples of acronyms; radar - RAdio Detecting And Ranging, sonar - SOunt NAvagation Ranging

Examples of abbreviations; IBM, XML</htmltext>
<tokenext>Pedantic , I know , but it 's a pet peeve with me .
Although SPICE could be a legitimate acronym , neither UML nor X would be acronyms , they would be abbreviations .
Examples of acronyms ; radar - RAdio Detecting And Ranging , sonar - SOunt NAvagation Ranging Examples of abbreviations ; IBM , XML</tokentext>
<sentencetext>Pedantic, I know, but it's a pet peeve with me.
Although SPICE could be a legitimate acronym, neither UML nor X would be acronyms, they would be abbreviations.
Examples of acronyms; radar - RAdio Detecting And Ranging, sonar - SOunt NAvagation Ranging

Examples of abbreviations; IBM, XML</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402132</id>
	<title>ta3o</title>
	<author>Anonymous</author>
	<datestamp>1260548760000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>-1</modscore>
	<htmltext>poor p8iorities,</htmltext>
<tokenext>poor p8iorities,</tokentext>
<sentencetext>poor p8iorities,</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402394</id>
	<title>more than 1 screen?</title>
	<author>MancunianMaskMan</author>
	<datestamp>1260549840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>are there any remote-desktoppy protocols/systems out there that do the Right Thing(TM) with a two-screen client machine?
I'd like to move to Terminal Services (or NoMachine/SPICE/Whatever) for performance reasons, but giving up on my niche 2 screens (one for IDE, one for the software i'm developing/testing to run on) would be kinda a step back.</htmltext>
<tokenext>are there any remote-desktoppy protocols/systems out there that do the Right Thing ( TM ) with a two-screen client machine ?
I 'd like to move to Terminal Services ( or NoMachine/SPICE/Whatever ) for performance reasons , but giving up on my niche 2 screens ( one for IDE , one for the software i 'm developing/testing to run on ) would be kinda a step back .</tokentext>
<sentencetext>are there any remote-desktoppy protocols/systems out there that do the Right Thing(TM) with a two-screen client machine?
I'd like to move to Terminal Services (or NoMachine/SPICE/Whatever) for performance reasons, but giving up on my niche 2 screens (one for IDE, one for the software i'm developing/testing to run on) would be kinda a step back.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30403490</id>
	<title>Re:Stop overloading common tech acronyms!</title>
	<author>IndustrialComplex</author>
	<datestamp>1260554160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>Yeah, and while we're at it, NASA: "Orion" means exploding nukes under a blast plate, not providing a cushy crew cabin.<nobr> <wbr></nobr>:)</i></p><p>I enjoy when the names they pick have myths that somewhat match the goals of the project.</p><p>So for the original 'Orion' would Hephaestus have been more appropriate?   What's a good myth for 'Lighting a fire under your ass'?</p><p>Project 'Wan Hu'?</p></htmltext>
<tokenext>Yeah , and while we 're at it , NASA : " Orion " means exploding nukes under a blast plate , not providing a cushy crew cabin .
: ) I enjoy when the names they pick have myths that somewhat match the goals of the project.So for the original 'Orion ' would Hephaestus have been more appropriate ?
What 's a good myth for 'Lighting a fire under your ass ' ? Project 'Wan Hu ' ?</tokentext>
<sentencetext>Yeah, and while we're at it, NASA: "Orion" means exploding nukes under a blast plate, not providing a cushy crew cabin.
:)I enjoy when the names they pick have myths that somewhat match the goals of the project.So for the original 'Orion' would Hephaestus have been more appropriate?
What's a good myth for 'Lighting a fire under your ass'?Project 'Wan Hu'?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402364</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401848</id>
	<title>Very cool I think.</title>
	<author>erktrek</author>
	<datestamp>1260547440000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>I currently use NXClient w/Neatx for that kind of remote access/management. It works well with both Linux and Windows backends.</p><p>I guess the difference is accessing various os's with a single protocol rather than using NX &amp; RDP (like the NXclient does) + also possibly getting around some of the builtin limitations (available only on certain flavors of Windows, limited # accesses by default etc) of RDP.</p><p>Sounds interesting if the performance is decent.</p></htmltext>
<tokenext>I currently use NXClient w/Neatx for that kind of remote access/management .
It works well with both Linux and Windows backends.I guess the difference is accessing various os 's with a single protocol rather than using NX &amp; RDP ( like the NXclient does ) + also possibly getting around some of the builtin limitations ( available only on certain flavors of Windows , limited # accesses by default etc ) of RDP.Sounds interesting if the performance is decent .</tokentext>
<sentencetext>I currently use NXClient w/Neatx for that kind of remote access/management.
It works well with both Linux and Windows backends.I guess the difference is accessing various os's with a single protocol rather than using NX &amp; RDP (like the NXclient does) + also possibly getting around some of the builtin limitations (available only on certain flavors of Windows, limited # accesses by default etc) of RDP.Sounds interesting if the performance is decent.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402398</id>
	<title>I attended a RHEL conference</title>
	<author>IMightB</author>
	<datestamp>1260549840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>where they demoed this and other VM technologies.  I think that RH has some really interesting VM Management stuff in the pipeline.    The nice thing about SPICE is your browser is the client.</p></htmltext>
<tokenext>where they demoed this and other VM technologies .
I think that RH has some really interesting VM Management stuff in the pipeline .
The nice thing about SPICE is your browser is the client .</tokentext>
<sentencetext>where they demoed this and other VM technologies.
I think that RH has some really interesting VM Management stuff in the pipeline.
The nice thing about SPICE is your browser is the client.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401898</id>
	<title>Re:Stop overloading common tech acronyms!</title>
	<author>betterunixthanunix</author>
	<datestamp>1260547680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>When I saw this story, I thought, "When did Red Hat enter the engineering design market?!"</htmltext>
<tokenext>When I saw this story , I thought , " When did Red Hat enter the engineering design market ? !
"</tokentext>
<sentencetext>When I saw this story, I thought, "When did Red Hat enter the engineering design market?!
"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401742
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401976
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30412172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30404638
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401898
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30403734
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30406138
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402562
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401636
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401608
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401870
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401608
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402442
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30403490
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402364
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401770
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401608
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30404332
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401998
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30403264
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30404954
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402540
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402488
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30408104
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402338
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402402
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402256
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30403362
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402338
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30403016
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401608
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_11_1339249_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401942
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401500
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_11_1339249.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401608
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30403016
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401870
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401770
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401636
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_11_1339249.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30405190
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_11_1339249.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401544
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402256
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402488
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402562
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30406138
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402402
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401976
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401742
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401998
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402364
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30403490
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30403264
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30404332
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402442
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30403734
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401898
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_11_1339249.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402394
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_11_1339249.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402338
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30403362
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30408104
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_11_1339249.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30405218
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_11_1339249.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30404638
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30412172
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_11_1339249.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30402540
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30404954
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_11_1339249.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30403522
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_11_1339249.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401500
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401942
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_11_1339249.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_11_1339249.30401604
</commentlist>
</conversation>
