🚀 go-pugleaf

Do you think that the Invalid Pointer Exception is coming from the client 
not being present?  The system I have setup should always have a client 
present; I typically (and my test rig is setup this way) only have two 
client's connected to the server application.  They both get the same 
messages no matter what and they should never leave (or disconnect from the 
server).  I can go through and make the server app more robust with the last 
suggestions but I know that I am getting an invalid pointer exception 
dealing with a SendText and the client didn't disconnect.  Also you stated 
earlier that I can't keep doing a sendtext until I get a ClientWrite Event 
after a -1 was returned from a SendText.  Now you are saying I have to do a 
SendText (pump the message queue) so I know the state of the socket.  I am 
sure I just don't understand what you said below because that doesn't make 
sense.  Thanks for the learning experience thus far.

Eric


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:444934c4$1@newsgroups.borland.com...
>
> "Eric Patterson" <eric.patterson@bepco.com> wrote in message
> news:44491a72$1@newsgroups.borland.com...
>
>>                         Server->WaitForClientWriteEvent = true;
>>                         while( Server->WaitForClientWriteEvent )
>>                         {
>>                                 Sleep(10);
>>                         }
>
> That will not work.  Non-blocking sockets use window messages internally.
> You must pump the message queue in order for those events to occur.  Which
> then complicates your code because now clients can connect/disconnect 
> while
> you are still looping through them, so your loop can become screwed up
> because your code is currently not set up to handle that situation.
>
>
> Gambit
>
>