[ENet-discuss] Unreliable Delivery for Large Messages

[Daniel Aquino]

Can't imagine it would be that difficult of a change.

On 5/27/11, Lee Salzman <lsalzman at gmail.com> wrote:
> For a suitable paypal donation I might be encouraged to add an unreliable
> fragment option. ;)
>
> On Fri, May 27, 2011 at 6:27 PM, Alexander Dolgansky
> <alexd221 at gmail.com>wrote:
>
>> Yes that's one of the options that I currently looking at.
>>
>> The reason why I need it in my project is because I have a large
>> number of data points that need to be sent out as one message at a
>> certain rate.
>> Therefore, each message needs to be sent out only once to keep up with
>> the overall sending rate. If message pieces arrive out of order or it
>> is not possible to send out
>> all of the pieces due to network issues, the whole message must be
>> dropped. This is the required behavior for some of the messages that I
>> need to transfer between nodes.
>>
>> Although splitting the data into smaller chucks is a valid solution to
>> my problem, I am wondering if ENet can do it for me.
>> After all, ENet already fragments any message that is larger than MTU,
>> so it is just a matter of figuring out how I can force ENet to
>> send fragments unreliably.
>>
>> Is it possible to accomplish what I am trying to do with ENet with
>> only minor changes to the source code?
>>
>> If yes, I would love to get pointers on how I should modify the source
>> code.
>>
>> Thanks.
>>
>> Alexander.
>> _______________________________________________
>> ENet-discuss mailing list
>> ENet-discuss at cubik.org
>> http://lists.cubik.org/mailman/listinfo/enet-discuss
>>
>

-- 
Sent from my mobile device