home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.windows.x:15146 comp.windows.x.intrinsics:181
- Newsgroups: comp.windows.x,comp.windows.x.intrinsics
- Path: sparky!uunet!decwrl!zazen!news
- From: daerb@vms.macc.wisc.edu (David Erb)
- Subject: Question: should I use the ConnectionNumber() macro?
- Message-ID: <1992Aug12.114716.24783@macc.wisc.edu>
- Sender: news@macc.wisc.edu (USENET News System)
- Organization: University of Wisconsin Academic Computing Center
- Date: 12 AUG 92 06:46:28
- Lines: 32
-
- I would like to use the following technique, but have heard
- mixed rumblings about its advisability:
-
- use "ConnectionNumber(display)" in a select() call with some
- other sockets to wait for messages from the X server while
- also waiting for messages on the other sockets.
-
- What's the party line on this technique?
-
- Is this portable across all Unix-like X client platforms?
-
- Is this portable across all X client platforms which support the
- select() mechanism?
-
- Are there examples of platforms where there is more than one
- socket used to implement the connection between a client and the
- server?
-
- Do I stand a chance of a race condition where I lose contact
- with the server?
-
- Any other wierd gotchas to watch out for?
-
- I'd love to hear any specific comments or advice.
-
- Any help and advice would be appreciated. Pointers
- to sources of other info would be great. Please
- e-mail me directly and I will post a summary.
- Thanks in advance.
-
- Dave
- daerb@macc.wisc.edu
-