Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!news.nd.edu!mentor.cc.purdue.edu!purdue!haven!adm!cmcl2!lanl!lanl.gov!dlc
From: dlc@c3.lanl.gov (Dale Carstensen)
Newsgroups: comp.windows.x
Subject: R5 wish list (was Re: Reattachable X clients)
Message-ID: <17895@lanl.gov>
Date: 15 Mar 91 18:17:28 GMT
References: <19910301203957.6.BARMAR@OCCAM.THINK.COM> <JANSSEN.91Mar7193448@holmes.parc.xerox.com>
Sender: news@lanl.gov
Reply-To: dlc@c3.lanl.gov (Dale Carstensen)
Lines: 18


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

I started a short discussion on "client recovery" a few months ago that was
a more limited version of this capability.  This sounds even better to me.
Will it be done?