[X2go-dev] EyeOS

Gerry Reno greno at verizon.net
Wed Feb 23 00:21:29 CET 2011


On 02/22/2011 05:59 PM, John A. Sullivan III wrote:
> On Tue, 2011-02-22 at 17:11 -0500, Gerry Reno wrote:
>   
>> On 02/22/2011 04:42 PM, John A. Sullivan III wrote:
>>     
>>> Hello, all.  I'd imagine none of us have the time to investigate this
>>> but I just took a quick look at EyeOS (http://www.eyeos.org).  It is an
>>> open source cloud desktop solution.  Version 2 was very slow and buggy
>>> but version 1 was amazingly fast.  
>>>   
>>>       
>> <snip>
>>
>> I don't remember if it was eyeos, but we looked at some of these "web
>> desktop integration" solutions a while back.
>>
>> It's not the same experience as having a "real" desktop. 
>>
>> Yes, they've managed to write some office-style apps and email clients
>> and other things. 
>>
>> But that does not truly duplicate a bona-fide native desktop.
>>
>> Many of the clients we pursue have very industry-specific software they
>> need to run. 
>> It needs to run the same whether we put it on their machines or ours in
>> the cloud. 
>>
>> With good remote access there's no retraining of users because they are
>> using the same software they've been using for years.  Just accessing it
>> remotely.
>>
>>
>> In the end, we opted to not go the WDI approach and instead looked for
>> good remote access technologies such as x2go that gives us the
>> flexibility to offer nearly any type of local/remote/cloud solution for
>> the client.
>>     
> <snip>
> That is exactly why we chose X2Go instead.  However, what caught my eye
> (no pun intended) was how responsive the video and sound were -
> significantly better than what we are doing in X2Go.  So, in the
> openness of open source, I wonder what we can learn from what they have
> done to improve X2Go - John
>
>   

Since most of these WDI offerings are browser-based my guess is that
they are passing a link down to the browser and accessing the video and
sound through an embedded media player directly rather than playing the
media on the server and then passing the output through to the client.

Just a guess.


Regards,
Gerry




More information about the x2go-dev mailing list