🚀 go-pugleaf

[stuff about SharedX]

>> 1) How does it handle heterogenous visual classes?
> Yes, you can share from mono to color and visa versa.  SharedX takes
> care of translating to protocol so you can share to a display of a
> different visual type.  SharedX will use whatever visual class the
> destination servers support.

>> 6) Does it allow new users to be brought in to existing "sharings"
>> of windows?  Can people leave and go as the please in a session?
> Yes users can be added and removed at any time, under the control of
> the "Sender" of the window.

Ummm.  So, it always presents a one-bit StaticGray visual to its
clients?  This seems to run counter to your response to question 1, but
since the protocol makes no provision for visuals suddenly disappearing
out from under existing connections, it seems to be the only way to
permit a typical one-bit workstation to join an existing session....

>> 2) How does it handle window management contention?
> The only window attribute that matters to the application is size.

You have a somewhat restricted notion of applications!  How do you deal
with windows whose bit-gravity is set to Static being moved on some but
not all of the servers, or being moved by different amounts?

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu