From: rick.jones2@hp.com   
      
   > > Yes.  getsockopt(...SO_ERROR...) is not going to do what you want.   
      
   > so why is it there?   
   > What type of Information does it yield?   
      
   If I were to guess, it might relate, at least in part, to the "errfds"   
   parm of select().  Most of the other socket calls have "side effects"   
   and if one simply select()ed for errors on the fd and select()   
   returned with one of those bits set, the getsockopt() would be a way   
   to retrieve that error without any side-effects.   
      
   In practice though, virtually all stacks will mark the fd as readable   
   (if that bit was set in readfds in the call that is) on return.   
      
   rick jones   
   --   
   No need to believe in either side, or any side. There is no cause.   
   There's only yourself. The belief is in your own precision.  - Joubert   
   these opinions are mine, all mine; HP might not want them anyway... :)   
   feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)