Re: Handling severe packet loss (serialization).
- From: Peter Duniho <no.peted.spam@xxxxxxxxxxxxxxxxxx>
- Date: Thu, 18 Mar 2010 09:56:57 -0700
jkv wrote:
Hi,
I am developing a application which have to continue working even in a
high packet loss environment, i have attached the serialization and
network transmission parts from both the server and client.
It works when there are no packet loss, but when introducing severe
packet loss (10%) it starts crashing because the ' int size =
br.ReadInt32();' in the server snippets reads some random data. [...]
What protocol are you using? TCP shouldn't have any trouble. If you're using UDP, switch to TCP or don't break your data across datagrams. If you're using TCP, then you've done something wrong, probably by making the incorrect assumption that the data will be delivered in the same groups in which it was sent.
Unfortunately, what little code you did post didn't show any of the actual network-related implementation details. It's not really possible to understand from your post why the "high packet loss environment" is causing trouble. But most likely, the answer will be: "use TCP, and use it correctly".
Pete
.
- Follow-Ups:
- Re: Handling severe packet loss (serialization).
- From: jkv
- Re: Handling severe packet loss (serialization).
- From: jkv
- Re: Handling severe packet loss (serialization).
- From: jkv
- Re: Handling severe packet loss (serialization).
- From: jkv
- Re: Handling severe packet loss (serialization).
- From: Steve Thackery
- Re: Handling severe packet loss (serialization).
- References:
- Prev by Date: Re: Globarlly use var (from linq) or anything equivalent ?
- Next by Date: Re: timer
- Previous by thread: Re: Handling severe packet loss (serialization).
- Next by thread: Re: Handling severe packet loss (serialization).
- Index(es):
Relevant Pages
|
