jeff@eagle.UUCP (Jeff Henslin) (03/07/88)
I am implementing an event driven application based on X, 10.4. What I would like to do is have my application interrupted ONLY when an event has occurred. Unfortunately, the X server will not send out event information to clients unless they are reading the socket and waiting for events. I can't block on a read (i.e. XNextEvent, etc.) or busy loop and check the socket myself as this defeats the purpose of my application. I looked for an o.s. call that would allow me to set the socket file descriptor so that it would appear to be ready for a write at all times but could not find one. Is there anyone who can tell me how to get around this problem? The other solution would be to start another process that monitors the socket and notifies my application when the socket should be read, but that seems like high overhead to me. Jeff Henslin XOX Corporation UUCP: ...!sun!sunlakes!xox!jeff ...!cornell!xox!jeff PHONE: (607) 277-6661