<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Hello,<br>
<br>
the topic "remote apps" can already be found on the mailinglist of the
project:<br>
<br>
<a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/archives/wayland-devel/2010-November/000037.html">http://lists.freedesktop.org/archives/wayland-devel/2010-November/000037.html</a><br>
<br>
I think Mark was also disappointed about the starting time of Xorg and
the change of resolution on startup. Together with the situation that
there are bad hardware implementations this may be a trigger for the
switch. <br>
<br>
But it won't be easy to access again all existing packets on debian
sid... I think this step can't be done with the next release...<br>
<br>
Regards,<br>
<br>
Heinz<br>
<br>
Am 07.11.2010 21:23, schrieb brian mullan:
<blockquote
cite="mid:AANLkTim3yTiAz4pwD72fBrhjG5PL7cuJUHsCrw1heKRV@mail.gmail.com"
type="cite"><br>
<div class="gmail_quote">Gerry <br>
<br>
Good questions, but I think they would be best asked on the forums
related to the projects (ubuntu and wayland)?<br>
<br>
<br>
Message: 2<br>
Date: Sat, 06 Nov 2010 11:14:01 -0400<br>
From: Gerry Reno <<a moz-do-not-send="true"
href="mailto:greno@verizon.net">greno@verizon.net</a>><br>
To: <a moz-do-not-send="true" href="mailto:x2go-dev@lists.berlios.de">x2go-dev@lists.berlios.de</a><br>
Subject: Re: [X2go-dev] How Wayland will handle X client & server<br>
Message-ID: <<a moz-do-not-send="true"
href="mailto:4CD570B9.6060003@verizon.net">4CD570B9.6060003@verizon.net</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
On 11/06/2010 08:44 AM, brian mullan wrote:<br>
> The Wayland FreeDesktop.org site<br>
> <<a moz-do-not-send="true"
href="http://wayland.freedesktop.org/architecture.html" target="_blank">http://wayland.freedesktop.org/architecture.html</a>><br>
><br>
> gives a good description of how Wayland will work and how it is<br>
> supposed to support legacy X client/server transparently.<br>
><br>
><br>
><br>
<br>
Having read through that site nowhere does it say that the Wayland
protocol is a network-aware protocol with the capabilities of the<br>
X-protocol. It appears that in order to use full network-aware remote
displays that it still relies on an X-server and X-client. If that is<br>
the case then there's not much to see here. Just maybe some
undetermined performance improvement but at what expense? There are no<br>
feature-by-feature or performance comparisons offered. Just a
presentation of "oh look, we can wire up some existing things<br>
differently without using X".<br>
<br>
So let me ask, where does the GPU acceleration processing take place?
If Wayland can support transparent network display clients using the<br>
X-protocol (so we don't have to reinvent the world) and make use of
local (client) GPU hardware to speed rendering then this would be<br>
great. But I haven't read that yet so I'm not very impressed at the
moment.<br>
<br>
Regards,<br>
Gerry<br>
<br>
<br>
</div>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
X2go-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:X2go-dev@lists.berlios.de">X2go-dev@lists.berlios.de</a>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/x2go-dev">https://lists.berlios.de/mailman/listinfo/x2go-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>