[ENet-discuss] Reliable packets and data sending approaches

[Nuno Silva]

Regarding the first part, AFAIK, ENet sends, a sequence number, so a packet
with the same sequence number would be dropped once one of them has been
acknowledged by the peer. So there's no danger in sending the same packet
twice. Just remember, ENet does that for you.

Regarding the second part, you should use both event-based notifying and
unreliable player movement packets. You should receive and send packets only
a few times per second unless they're events though, like in the Source
Engine's networking, where they send packets 20 times per second regarding
user input. 20 times per second should be a good starting point for you to
experiment on.

Good luck,
Nuno Silva.

On Mon, Oct 26, 2009 at 8:31 PM, Philip Bennefall
<philip at pbsoundscape.net>wrote:

>  Hi Lee and others,
>
> I have a quick question regarding reliable packets. Say that user 1 sends a
> message to user 2 on channel 0, and it gets through on the first attempt.
> Does user 2 see the packet immediately or does ENet wait until the package
> has been acknowledged? And what happens if user 1 doesn't receive the
> acknowledgement and then sends the packet again eventually, and this packet
> also arrives, might user 2 be given the same packet twice?
>
> Also I am wondering about the best way of sending data. I am making a fast
> paced action game with two players, where speed is of the utmost importance.
> Is it best to send individual events when they occur, or continuously send
> the entire player state unreliably? If the latter, how often should I send
> it? I was thinking at least 40 times a second, as the state isn't larger
> than some 60 or 70 bytes. Do you have any recommendations?
>
> Thank you!
>
> Kind regards,
>
> Philip Bennefall
> P.S. I am using the latest snapshot.
>
> _______________________________________________
> ENet-discuss mailing list
> ENet-discuss at cubik.org
> http://lists.cubik.org/mailman/listinfo/enet-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cubik.org/pipermail/enet-discuss/attachments/20091026/a722f943/attachment.htm>