Gerry
Good questions, but I think they would be best asked on the forums related to the projects (ubuntu and wayland)?
Message: 2 Date: Sat, 06 Nov 2010 11:14:01 -0400 From: Gerry Reno <greno@verizon.net> To: x2go-dev@lists.berlios.de Subject: Re: [X2go-dev] How Wayland will handle X client & server Message-ID: <4CD570B9.6060003@verizon.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 11/06/2010 08:44 AM, brian mullan wrote:
The Wayland FreeDesktop.org site <http://wayland.freedesktop.org/architecture.html>
gives a good description of how Wayland will work and how it is supposed to support legacy X client/server transparently.
Having read through that site nowhere does it say that the Wayland protocol is a network-aware protocol with the capabilities of the 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 the case then there's not much to see here. Just maybe some undetermined performance improvement but at what expense? There are no feature-by-feature or performance comparisons offered. Just a presentation of "oh look, we can wire up some existing things differently without using X".
So let me ask, where does the GPU acceleration processing take place? If Wayland can support transparent network display clients using the 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 great. But I haven't read that yet so I'm not very impressed at the moment.
Regards, Gerry
They are. These types of questions are now starting to show up on many forums. I also found a whole thread on this over at the Fedora development forum. They were also asking these same types of things and much more in technical detail. All of which is good. For something that is going to have a huge impact on the Linux community I think getting input from all quarters is absolutely essential. I think a lot of this Wayland stuff got started only because people were frustrated with the pace of changes by X. But despite some of the issues concerning X the X guys have done a good job of maintaining compatibility for a huge number of systems for many years. And when you're doing that, the pace has to be deliberate and considered.
Regards, Gerry
On 11/07/2010 03:23 PM, brian mullan wrote:
Gerry
Good questions, but I think they would be best asked on the forums related to the projects (ubuntu and wayland)?
Message: 2 Date: Sat, 06 Nov 2010 11:14:01 -0400 From: Gerry Reno <greno@verizon.net <mailto:greno@verizon.net>> To: x2go-dev@lists.berlios.de <mailto:x2go-dev@lists.berlios.de> Subject: Re: [X2go-dev] How Wayland will handle X client & server Message-ID: <4CD570B9.6060003@verizon.net <mailto:4CD570B9.6060003@verizon.net>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 11/06/2010 08:44 AM, brian mullan wrote:
The Wayland FreeDesktop.org site <http://wayland.freedesktop.org/architecture.html>
gives a good description of how Wayland will work and how it is supposed to support legacy X client/server transparently.
Having read through that site nowhere does it say that the Wayland protocol is a network-aware protocol with the capabilities of the 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 the case then there's not much to see here. Just maybe some undetermined performance improvement but at what expense? There are no feature-by-feature or performance comparisons offered. Just a presentation of "oh look, we can wire up some existing things differently without using X".
So let me ask, where does the GPU acceleration processing take place? If Wayland can support transparent network display clients using the 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 great. But I haven't read that yet so I'm not very impressed at the moment.
Regards, Gerry
X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Hello,
the topic "remote apps" can already be found on the mailinglist of the project:
http://lists.freedesktop.org/archives/wayland-devel/2010-November/000037.htm...
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.
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...
Regards,
Heinz
Am 07.11.2010 21:23, schrieb brian mullan:
Gerry
Good questions, but I think they would be best asked on the forums related to the projects (ubuntu and wayland)?
Message: 2 Date: Sat, 06 Nov 2010 11:14:01 -0400 From: Gerry Reno <greno@verizon.net <mailto:greno@verizon.net>> To: x2go-dev@lists.berlios.de <mailto:x2go-dev@lists.berlios.de> Subject: Re: [X2go-dev] How Wayland will handle X client & server Message-ID: <4CD570B9.6060003@verizon.net <mailto:4CD570B9.6060003@verizon.net>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 11/06/2010 08:44 AM, brian mullan wrote:
The Wayland FreeDesktop.org site <http://wayland.freedesktop.org/architecture.html>
gives a good description of how Wayland will work and how it is supposed to support legacy X client/server transparently.
Having read through that site nowhere does it say that the Wayland protocol is a network-aware protocol with the capabilities of the 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 the case then there's not much to see here. Just maybe some undetermined performance improvement but at what expense? There are no feature-by-feature or performance comparisons offered. Just a presentation of "oh look, we can wire up some existing things differently without using X".
So let me ask, where does the GPU acceleration processing take place? If Wayland can support transparent network display clients using the 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 great. But I haven't read that yet so I'm not very impressed at the moment.
Regards, Gerry
X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
-
brian mullan -
Gerry Reno -
Heinz-M. Graesing