Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!uwm.edu!bionet!parc!janssen From: janssen@parc.xerox.com (Bill Janssen) Newsgroups: comp.windows.x Subject: Re: Reattachable X clients Message-ID: Date: 8 Mar 91 03:34:48 GMT References: <19910301203957.6.BARMAR@OCCAM.THINK.COM> Sender: news@parc.xerox.com Organization: Xerox PARC, Palo Alto, CA Lines: 24 In-Reply-To: barmar@think.COM's message of 1 Mar 91 20:39:00 GMT In article <19910301203957.6.BARMAR@OCCAM.THINK.COM> barmar@think.COM (Barry Margolin) writes: > I'd > like to be able to move my X clients from one display to another (for > instance, if I had a home X terminal I'd want to bring my windows home > with me), or reboot my workstation without having to kill all the remote > X clients (saving local clients across reboots is outside the scope of > X). X clients communicate with their server via a "display" abstract > data type; this object hides the details of the communication protocol, > allowing the same clients to work over TCP, DECnet, shared memory, etc. > Thus, it should be possible for them to disconnect themselves from the > transport mechanism completely, and later open a new transport > connection and use that. Yes, GNU Emacs xx.xx (for X10) had an interface that allowed this. I've never understood why this isn't a basic capability for X toolkits. The MCC CommonLisp/X toolkit, DWS, certainly allowed this. Bill -- Bill Janssen janssen@parc.xerox.com (415) 494-4763 Xerox Palo Alto Research Center 3333 Coyote Hill Road, Palo Alto, California 94304