[Spice-devel] Spice for commercial use

[Marian Krcmarik]

----- Original Message -----
> From: "John A. Sullivan III" <jsullivan at opensourcedevel.com>
> To: spice-devel at lists.freedesktop.org
> Sent: Thursday, March 7, 2013 2:35:10 PM
> Subject: Re: [Spice-devel] Spice for commercial use
> 
> On Thu, 2013-03-07 at 01:10 -0800,
> spice-devel-request at lists.freedesktop.org wrote:
> > Date: Wed, 6 Mar 2013 06:24:34 -0800
> > From: Tom Holmes <tomholmes at live.com>
> > To: <spice-devel at lists.freedesktop.org>
> > Subject: [Spice-devel] Spice for commercial use
> > Message-ID: <BLU170-W120A85A49F95B3126C2236EC5E40 at phx.gbl>
> > Content-Type: text/plain; charset="iso-8859-1"
> > 
> > 
> > Hello!
> > Can Spice be used for commercial use, if so are there licensing
> > fees
> > that are applied?  Would you say Spice is comparable to RDP, ICA
> > and
> > PCOIP?  Can Spice be used to access a Windows Desktop?
> > Thank you so much!Tom
> > 
> I have not used PCoIP but, from what I understand, SPICE would be
> most
> similar to that.  Fundamentally, all four are providing the same
> primary
> functionality - remote desktops.  In my experience, RDP and ICA are a
The goal is the same but concept how to achieve it is (afaik) completely different. PCoIP is a UDP stream of rendered pixels on host (with some support to offload image encoding to special hardware cards) while Spice is a TCP stream of graphics commands to be rendered on the client.
> little more responsive over a WAN/Internet connection right now but
> do
> not handle multimedia as well as SPICE.  I mean RDP6 and above - RDP5
> was terrible over a WAN.  I believe, as video becomes more important
> and
> as SPICE improves its video capability, perhaps with an inter-frame
> compression algorithm instead of MJPEG, it will become our remote
> desktop protocol of choice :) - John
> 
> _______________________________________________
> Spice-devel mailing list
> Spice-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/spice-devel
>