| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
If you establish a socket as "non-blocking", will a select
block just the thread or the entire user process?
Robin
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1342.1 | TOOK::SWIST | Jim Swist LKG2-2/T2 DTN 226-7102 | Thu Aug 15 1991 12:34 | 10 | |
You don't have to do any of the non-blocking stuff.
If you include file cma_ux.h, it will redefine all the ultrix I/O
functions as cma wrappers (e.g. socket->cma_socket). The CMA
wrappers transparently convert the blocking I/O to non-blocking. The
CMA idle thread then sits on a select() for all the outstanding I/O
operations and resumes the threads as their I/O completes.
Obviously you can do this yourself, but since the work has been done
by CMA, why not use it?
| |||||