🚀 go-pugleaf

Gambit

The problem I was having was a software exception (0x0eedfade) occured in 
the application at the location 0x7c81e633.  I found after some research 
that this usually shows up when a linked dll has an excpetion which isn't 
being handled.  I removed a dll which I was temporary using to track memory 
sector overwrites; since I have never seen that error until now.  That 
exception has gone away and since in this process of finding my problems I 
removed clearing the errorcode integer on a Socket OnError event, I came in 
this morning with an asynchronous socket error 10053 which I already know is 
what the socket throws back to me when it is full and busy.  I would of 
expected this error soon after starting the app but it didn't occur until 5 
hours later.  I will make the additions now that when I see a 10053 in the 
OnError event to wait for a ClientWrite Event to occur before continuing on; 
like we have discussed before.

Eric


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:44480b3f$1@newsgroups.borland.com...
>
> "Eric Patterson" <eric.patterson@bepco.com> wrote in message
> news:4447d8b4$1@newsgroups.borland.com...
>
>> I did do the change and I am getting different problems now
>> which I am trying to fix
>
> What problems are you having now?  Please elaborate.
>
>> if SendText doesn't send the entire amount and I fill the socket buffer
>> wouldn't it call the ServerSocket OnError event?
>
> No.  The OnError event is only triggered for actual socket errors.  A
> blocking send is not an error.  WSAEWOULDBLOCK will never trigger the
> OnError event.
>
>
> Gambit
>
>