Jimmy_Guse.NSD@LCCMAIL.OCF.LLNL.GOV (Jimmy Guse) (03/20/91)
Reply to: RE>TNetListen and socket descr > Your exchange about TNetListen and socket descriptors caught my eye, but I > don't really understand the problem or the solution, I'm afraid! >>> My problem is I need to get the listen socket number after performing >>> the TNetListen call. > Pure curiosity: presumably you want to get the socket descriptor *before or > without* a call to TNetAccept - why ? It goes back to the fact that ISODE doesn't support multi-tasking. The idea is to do a central non-blocking select instead of waiting in TNetAccept -- for which one requires a file-descriptor > What is it about the nature of sockets and the way descriptors are > allocated that enables you to guarantee that this will be the case ? > If this is the case normally, would it also work when setjmp() and > longjmp() are used, as they are in ISODE ? I am curious about this. Is it reasonable to assume that the underlying descriptor allocation strategy will always behave this way? BSD and SysV, etc. Thanks, Jimmy guse@llnl.gov