On Tue, 2010-11-09 at 17:55 +0000, Jeff Spaleta wrote: > On Tue, Nov 9, 2010 at 4:55 PM, Adam Jackson <ajax@xxxxxxxxxx> wrote: > > Remoting a wayland application is _trivial_. Either to an X or to a > > wayland view system. It's hard to make wayland remoting less flexible > > than X over the network, since the natural remoting level (surface > > updates) is basically stateless unlike X's sixteen complete IPC > > interfaces, and unlike X you're actually guaranteed that the window > > surfaces exist and have meaningful content. So you get the > > long-lusted-for "screen for X" almost for free. > > I think what's missing is a concrete demonstration to point to of > remoting of a Wayland native client window to wrap our heads around > how different (easy or hard) it is. When the time comes to introduce > initial wayland packages into Fedora having the ability to demonstrate > a native toy Wayland client rendered remotely (and securely from say > a virtualized host) is probably something to shoot for. The UX will probably be somewhere between ssh -Y, vncserver(1), and: https://bugzilla.redhat.com/show_bug.cgi?id=651591 - ajax
Attachment:
signature.asc
Description: This is a digitally signed message part
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
