Re: C# Async Socket timeouts
- From: "Peter Duniho" <NpOeStPeAdM@xxxxxxxxxxxxxxxx>
- Date: Wed, 28 May 2008 13:52:22 -0700
On Wed, 28 May 2008 13:06:38 -0700, <ColoradoGeiger@xxxxxxxxx> wrote:
I have many reasons for not getting a response, and TCP issues are not
the most likely.
It really doesn't matter why you don't get a response. The way TCP works, either the data will remain ordered as I describe, or you've got a broken TCP implementation.
If the latter is the case, you probably shouldn't be using TCP. Doing so will only cause huge headaches down the road, because all of the non-specialized parts of your communications network will not understand or allow for a broken TCP implementation.
Pete
.
- References:
- C# Async Socket timeouts
- From: ColoradoGeiger
- Re: C# Async Socket timeouts
- From: Jeroen Mostert
- Re: C# Async Socket timeouts
- From: ColoradoGeiger
- Re: C# Async Socket timeouts
- From: Peter Duniho
- Re: C# Async Socket timeouts
- From: ColoradoGeiger
- C# Async Socket timeouts
- Prev by Date: Re: Interfaces and Inheritance
- Next by Date: Re: Question about return style
- Previous by thread: Re: C# Async Socket timeouts
- Next by thread: Question about return style
- Index(es):
Relevant Pages
|