On Sun, 30 Nov 2008 19:34:41 -0600, John McKown wrote: > >Quite often, in the UNIX world, what is done is that the main process >(task) will do all of this. It will then fork() or spawn() another process >and give ownership of the socket created above to that process. The new >process (called the child) will do all the TCPIP functions that need to be >done. > Isn't the statement "give ownership of the socket" superfluous? I think a socket is just a variety of descriptor which fork() automatically replicated in the child process space. What may be important is that the parent close() its instance of that descriptor in order that the client can detect the close() by the child.
"in the UNIX world"??? Isn't z/OS Unix? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
