Re: Socket question

Scott:

> 
> The exception set has nothing to do with network errors.
> 

I must admit that a lot of what I know (or what I think I know) came
from your tutorial and the following lines confused me:

 
C*===============================================================
         C*  This loads any data that has been sent by the various
client
         C*  sockets into their respective read buffers, and also checks
         C*  for clients that may have disconnected:
 
C*===============================================================
......
         c                   if        FD_ISSET(sock: readset)
         c                   if        ReadClient(C) < 0
         c                   callp     EndClient(C)
         c                   callp     FD_CLR(sock: excpset)
         c                   endif
         c                   endif
         c                   if        FD_ISSET(sock: excpset)
         c                   callp     EndClient(C)
         c                   endif
.......

I had always assumed (and you know what happens when we assume...) that
the part of code that check for disconnected clients was the line that
checked excpset, but you are saying that it is the return of
(ReadClient(C) < 0) when we know that there is data in the buffer?

> but then I don't work with handhelds.  
Lucky you ;)

> actually mean that the connection is ALIVE, rather than the opposite. 

Knowing that I had never sent OOB data in the handheld application,
should I even bother checking excpset?  My only _guess_ as to why I am
getting OOB data is because it is M$ .Net is doing it for me somewhere
under the covers?

Thanks again for all your help,
Andy