| |||||||||||||
Wayland and Weston 1.0 releasedWayland and Weston 1.0 releasedPosted Oct 25, 2012 15:36 UTC (Thu) by gidoca (subscriber, #62438)In reply to: Wayland and Weston 1.0 released by nix Parent article: Wayland and Weston 1.0 released
As far as I understand from the XDC presentation video, it wouldn't be implemented in the toolkit, but as a special wayland compositor. On the computer you want to display the window, you would run the regular weston compositor, plus some client software. On the machine the application runs on, you would instead run some special compositor that speaks the wayland protocol, but sends the buffer over the wire instead of displaying it on the local display. Therefore, you wouldn't need anything special in the toolkit. Note that I don't know any more than what I learned from the talk, so take this with a grain of salt.
(Log in to post comments)
Wayland and Weston 1.0 released Posted Oct 28, 2012 15:58 UTC (Sun) by nix (subscriber, #2304) [Link]
That's the fallback remoter, I think. The *real* remoting would be done in the toolkits, which know exactly what the application has done and can transmit data over the wire with correspondingly high efficiency, just as X does now only actually efficiently. (I hope there'll be a library of some sort implementing authentication and such things, so that the different toolkits don't end up with divergent ways of authenticating the remote connection with different user interfaces. xauth-plus-ssh is bad enough as it is...)
Wayland and Weston 1.0 released Posted Nov 1, 2012 19:22 UTC (Thu) by wmf (guest, #33791) [Link]
I think toolkit remoting is going to be much more complex (especially when you have to implement it N times) and not necessarily faster than bitmap remoting (cf. the Sun Labs SLIM project). Also, it creates more bad PR because it makes it look like Wayland remoting is five years away.
|
|||||||||||||