Path: utzoo!attcan!uunet!crdgw1!uakari.primate.wisc.edu!samsung!cs.utexas.edu!bcm!wilkins.iaims.bcm.tmc.edu!etaylor
From: etaylor@wilkins.iaims.bcm.tmc.edu (Eric Taylor)
Newsgroups: comp.windows.x
Subject: Re: Interclient Communication
Keywords: Property SendEvent ClientMessage
Message-ID: <2433@gazette.bcm.tmc.edu>
Date: 25 Oct 90 14:45:17 GMT
References: <880@kivax.UUCP>
Sender: usenet@bcm.tmc.edu
Reply-To: etaylor@wilkins.iaims.bcm.tmc.edu (Eric Taylor)
Lines: 32
Nntp-Posting-Host: wilkins.iaims.bcm.tmc.edu

In article <880@kivax.UUCP>, koe@kivax.UUCP (Diana Koehler) writes:
|> I am just working with the different mechanisms of 
|> interclient communication.
|> What method should I use
|> -  to exchange data between clients ?
|>    (Properties or XSendEvent, with type ClientMessage)
|> -  to notify a client without sending data (in sense of semaphores)
|> 
|> 
|> Thanks
|> 
|> 
|> Diana
|> 
|> ------------------------------------------------------------------------
|> 
|> Diana Koehler                     Tel.:   +49 7721 867034
|> Mannesmann Kienzle GmbH
|> Abt. 011.2                        e-mail: koe@kivax.UUCP
|> Postfach 1640                             ..!mcsun!unido!kivax!koe
|> D-7730 VS-Villingen                       ..!uunet!unido!kivax!koe


If you have large amounts of data, you should probably not use
X for your communication (fairly slow).  Instead, have one application create a socket and send the port # (via X) to the client that you wish to communicate with.  Then use simple reads and writes to communicate.  Obviously not as portable as X but sometimes the speed can demand it.

Client notification is handled nicely with XSendEvent(ClientMessage).
-- 
					Eric Taylor
					Baylor College of Medicine
					etaylor@wilkins.bmc.tmc.edu
					(713) 798-3776