Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: XSelectEvent()...
Message-ID: <8903211457.AA00395@EXPIRE.LCS.MIT.EDU>
Date: 21 Mar 89 14:57:27 GMT
References: <142@mirsa.inria.fr>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 15


    now my question is: 
       - what is right and what is wrong when using SendEvent request
	for X client communications ?

I'm afraid the best I can muster is "I usually know it when I see it".

    Each time an xtalk receives a keypress event on the first window, it must 
    echo it "locally" and send a request to all other xtalk processes, saying 
    that they must also echoing that character in their own sender's window.

One argument would be: there's no particular reason why you should restrict
this interaction to *only* X user interfaces.  Shouldn't xtalk be able to
communicate with talk programs displaying on terminals or other window systems?
In that case, using SendEvent for inter-talk IPC is clearly wrong.