[ENet-discuss] how to know when it's safe to call enet_peer_send

[Ruud van Gaal]

It seems you may want to change ENET_PROTOCOL_MAXIMUM_WINDOW_SIZE, although
I'm not sure what it does. :)

I have had similar problems where I wanted to modify disconnect timeouts.
I've modified the source so I can change ENET_PEER_TIMEOUT_MINIMUM and
ENET_PEER_TIMEOUT_MAXIMUM to the applications preference. In one app (a
lobby server) the short timeouts are ok, but for another app (LAN-based)
there can be delays of ~30s in calling enet).

Is it an idea (Lee?) to put most of those tuning settings in an ENetPrefs
structure so you can modify them before initializing Enet? It seems for GPRS
for example you'll need slightly tuned settings.

Cheers,
Ruud

> Date: Tue, 18 Mar 2008 00:25:50 +0300
> From: eye at dihalt.com
> Subject: Re: [ENet-discuss] how to know when it's safe to	call
> 	enet_peer_send()?
> To: Discussion of the ENet library <enet-discuss at cubik.org>
> Message-ID: <web-3357404 at backend14.aha.ru>
> Content-Type: text/plain; charset="ISO-8859-1"
> 
> I have just tested the code. There is a little problem:
> peer->windowsSize is a constant value of
> ENET_PROTOCOL_MAXIMUM_WINDOW_SIZE (32768) if network speed is 
> not set. And i can't set or test network speed for end-user 
> programs - speed can be very different each minute. 32768 is 
> a big value. On slow GPRS networks and medium size packets 
> (~1k) sending 32768/1024 = 32 packets will surely lead to ACK 
> timeout :(.