[ENet-discuss] ENet 2.0 most wanted features?

[Nuno Silva]

Maybe if there was a way to set an optional packet type group flag on a
packet and set up a rule depending on the packet type group, that would
work. For instance, having a packet type group POSITION_UPDATE, set a rule
for the packets like LAST_PACKET_ALWAYS_RELIABLE so if you stop sending the
positions it'll keep resending the last while keeping all others as
unreliable.


On Tue, Apr 30, 2013 at 4:51 PM, Thorbjørn Lindeijer <bjorn at lindeijer.nl>wrote:

> On Tue, Apr 30, 2013 at 3:10 PM, Doug Warren <dwarren at thebigwave.net>
> wrote:
> > New packet type of best effort last message of a channel:  Any message
> for
> > the channel would be unreliable but if we're sending a packet and the
> last
> > acknowledged received sequence number is less than the last sent sequence
> > number for that channel, a copy is sent anyway.  This could be used for
> > frequently changing things like position but if there's room you'll get
> the
> > most recent position anyway.
>
> I second this. For example when sending position updates only when the
> position changed, it would be very useful if they could be sent
> "unreliable" while still guaranteeing that the last update will
> arrive.
>
> Though I guess if it is per-channel then one could only do this for up
> to about 256 entities. Maybe it would be better if there was a way to
> manually mark a sent packet as "stop trying to resend", or in any case
> some way to remove / replace it.
>
> Regards,
> Bjørn
> _______________________________________________
> 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/20130430/b5f301f0/attachment.html>