[X2go-dev] wayland remote desktop comment by

John A. Sullivan III jsullivan at opensourcedevel.com
Thu Feb 3 17:40:52 CET 2011


On Thu, 2011-02-03 at 10:54 -0500, Gerry Reno wrote:
> On 02/03/2011 09:35 AM, John A. Sullivan III wrote:
> > On Thu, 2011-02-03 at 09:19 -0500, brian mullan wrote:
> >   
> >> Per Wayland FAQ: Is Wayland network transparent / does it support
> >> remote rendering?
> >> No, that is outside the scope of Wayland. <snip>
> >>
> >>
> >> It is also possible to put a remoting protocol into a wayland
> >> compositor, either a standalone remoting compositor or as a part of a
> >> full desktop compositor. This will let us forward native Wayland
> >> applications. The standalone compositor could let you log into a
> >> server and run an application back on your desktop. Building the
> >> fowarding into the desktop compositor, could let you export or share a
> >> window on the fly with a remote wayland compositor, for example a
> >> friends desktop.
> >>     
> > <snip>
> > I am WAY out of my depth here but that last paragraph is really
> > interesting and I wonder if it provides an opportunity for X2Go to think
> > outside the box.  Why do we need NX? To forward X traffic in a WAN
> > friendly way to the remote X Server.  So, what if we bypass it
> > completely - completely eliminate the need to transmit, cache, compress,
> > optimize X traffic.  Does the above mean we can just us our SSH
> > forwarding to send the Wayland traffic to a compositor on the remote
> > side and not worry about X over a network? - John
> >
> >   
> 
> Nope.  Wayland is not network transparent.
> 
> For network transparency you would still have to layer X on top of Wayland.
> 
<snip>
That part I get but what do they mean with they speak of communicating
with a remote compositor and thus being able to forward native Wayland
applications? - John




More information about the x2go-dev mailing list