Re: CSocket, best way to wait for a reply?
- From: "simon" <spambucket@xxxxxxxxxxxx>
- Date: Thu, 7 Apr 2005 19:12:42 +0100
"Joseph M. Newcomer" <newcomer@xxxxxxxxxxxx> wrote in message
news:8qv951p1i7gv6r3pa7moenu666ip7qsjgo@xxxxxxxxxx
> Well, your first mistake is using CSocket. You already have a situation
> that is, as far as
> I am concerned, completely unrecoverable and unsalvageable. Lose the
> CSocket entirely, and
> use CAsyncSocket. CSocket ranks among the worst possible ways to implement
> network
> communication.
>
> As far as I'm concerned, until CSocket is completely removed and you
> rewrite your code to
> use CAsyncSocket, you have a program that is guaranteed to fail in ways
> that are
> unrecoverable.
>
Well, I changed to CAsyncSocket and it seems to be a lot more stable.
But I still need to run some tests to make sure.
I am worried that I am "hoping" the system works rather than "Knowing" the
system works.
Simon
.
- Follow-Ups:
- Re: CSocket, best way to wait for a reply?
- From: Scott McPhillips [MVP]
- Re: CSocket, best way to wait for a reply?
- References:
- CSocket, best way to wait for a reply?
- From: simon
- Re: CSocket, best way to wait for a reply?
- From: Joseph M . Newcomer
- CSocket, best way to wait for a reply?
- Prev by Date: Threads + Static Member Functions
- Next by Date: Re: Threads + Static Member Functions
- Previous by thread: Re: CSocket, best way to wait for a reply?
- Next by thread: Re: CSocket, best way to wait for a reply?
- Index(es):
Relevant Pages
|