Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!mcsun!hp4nl!crione!aba
From: aba@crione.UUCP (Katie Boyle's Problem Page)
Newsgroups: comp.windows.x
Subject: Re: Robust multi-display clients
Message-ID: <192@crione.UUCP>
Date: 15 May 91 13:30:04 GMT
References: <WALT.91May4173316@arrisun3.utarl.edu>
Reply-To: aba@crione.UUCP (Katie Boyle's Problem Page)
Distribution: comp
Organization: CRI A/S, Leiden, Netherlands
Lines: 22

In article <WALT.91May4173316@arrisun3.utarl.edu> Buehring@Intellection.COM (Walt Buehring) writes:
>Question (in a nutshell):
>
>How do *you* go about writing an X application that displays windows on
>many X servers, is insensitive to remote server crashes, provides
>reasonable interactive response time to all users, and does not
>consume oceans of virtual memory?
>
>

Could you try splitting the application into separate processes
and then communicating via the Motif Clipboard? Or perhaps use
"raw" property communication without the Clipboard. I've used properties
for Inter Client Communication successfully, but only within the same
display.

If the system has shared libraries, or will have them in future,
then the problems with the sizes of Xm, Xt and X11 are not (will not be)
so bad. If the application is distributed across many displays, then the
memory usage is also distributed.

ABA