"Angela Bodnar" <angela.bodnar@noris.org> wrote in message
news:45b792c7$1@newsgroups.borland.com...
> I really didn't think you wanted to see thousands of lines of
> code from me.
I don't. Which is why you need to trim it down to the most bare-bones
eample you can that still reproduces the same problem.
> I was just trying to find out if there was a known problem of this
type.
This is not a socket problem. A socket does not use the CPU that
hard. Which is why I suspect your own code is faulty somewhere.
> Sometimes the program will recover itself and reconnect after
> sensing a disconnect. Sometimes it can not recover and this
> is ususally accompanied with a socket error 10053 or 10054.
Those are normal errors for a socket that was abnormally disconected.
Gambit
