🚀 go-pugleaf

Hello one and all

Firstly, appologies to those who think this may be off topic for that 
group, but i'm hoping someone has come across this before.

Background:
Server and clinet socket application runing on windows 95.

Client can be telnet or finger.

Using Winsock or wsock32 from M$. Using sockets dll with my own C++ 
wrapper i had before MFC around, so we're talking raw dll interface 
here. using Visual C++ but it won't make any difference here.

Problem:

I have a server - in this case on port 79 for finger but started as a 
problem in another application. Client connects to server and the server 
is required to send back some data then close the connection. If the 
closesocket or shutdown is called from with in either the FD_ACCEPT or 
the FD_READ it hangs the system. This can be with either a ligering 
shutdown or not, and is using WSAAsyncSelect. Ok. So i remove the close 
and put lots or debug trace statements in. I see there a quite a few 
meesages handled after the origonal FD_ACCEPT or FD_READ. So, at the 
begining of the handler, i put in an WSAAsyncSelect to select no more 
messages, but as the documentation points out, there can (and are) still 
messages in the queue to be handled.

I am now in the sistuation where i can not stop the messages. I do not 
know when the last one has been handled, and i do not know when all the 
data has been sent.

Has anyone seen this, got a work round.

M$ contacted but first line of defence was 'well these are important 
calls so they have been tested'....took me two hours on the phone to get 
that far.

Help please mucho.
-- 
MSN, Making the world smaller and taking it to Redmond!
Don't tell the FBI, but 'The Gates Cult' lives at Remond - the new WACO.
   __       
  /  )          David E Wood
 /  /_   * _ /  
/__/(_(|/|(_(   david@thermoteknix.co.uk