Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!hplabs!hpfcso!garfinkel
From: garfinkel@hpfcso.FC.HP.COM (Dan Garfinkel)
Newsgroups: comp.windows.x
Subject: Re: Request for info on X window sharing systems
Message-ID: <7320024@hpfcso.FC.HP.COM>
Date: 20 Jun 91 18:27:31 GMT
References: <1991May22.211831.5912@spectra.com>
Organization: Hewlett-Packard, Fort Collins, CO, USA
Lines: 25

> 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....

No.  The application still renders to the visual(s) on the senders system 
and SharedX takes care of translating the protocol to whatever visual is 
available on the receiver's system.  So if the application puts an image to a
4 bit pseudo-color device and that window is being shared to a 24 bit true
color device, SharedX will convert the image (including all the pixel values
in the image) to render properly on the destination server(s).  

> >> 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?

SharedX does not do a perfect job at sharing all applications.  This is 
just one example.  To does, however, do a very good job at sharing most
applications.

-Dan