Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!sbi!zeus!bpa_su10!sivan
From: sivan@bpa_su10.Sbi.Com (Sivan Mahadevan)
Newsgroups: comp.windows.x
Subject: Re: Interclient Communication
Keywords: Property SendEvent ClientMessage
Message-ID: <112@bpa_su56.bpa_su10.Sbi.Com>
Date: 30 Oct 90 21:33:06 GMT
References: <880@kivax.UUCP> <1506@pai.UUCP>
Organization: BPA - Salomon Brothers, NY
Lines: 22

In article <1506@pai.UUCP>, erc@pai.UUCP (Eric Johnson) writes:
> 
>      I'm assuming you mean you want to only send short messages
>      between your clients. The X Window System is not intended to
>      be a generic inter-process communication (IPC) system. If you want to
>      send large amounts of data, you'll probably have a better time
>      with sockets, streams, shared memory or some other
>      IPC technique.
> 

We do a lot of interclient communication here and find the need to
use different techniques (sockets, shared memory, signals, ClientMessage)
depending on the context.  A tip for those who might want to make Xlib
calls in signal handlers: we built a more "reentrant" Xlib by setting
the LockDisplay() and UnlockDisplay() macros in Xlib to block and
unblock, respectively,  relevant signals (e.g., SIGUSR1).

-- 
Sivan Mahadevan
Salomon Brothers Inc	Bond Portfolio Analysis		Analytical Applications Group
One New York Plaza	44th Floor			212-747-5418
New York NY 10004	sivan@bpa_su10.sbi.com		uunet!sbi.com!bpa_su10!sivan