And just in case you didn't get it, you can delete the data after you tell enet to send the packet, since enet creates it's own copy of the data.<br><br><div class="gmail_quote">On Fri, Dec 18, 2009 at 10:38 PM, Lee Salzman <span dir="ltr"><<a href="mailto:lsalzman1@cox.net">lsalzman1@cox.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Packets allocate their own copy of the data, so once you send them, you don't need to free anything since ENet handles that itself. However, the packets ENet gives to you on RECEIVE events, you must remember to destroy them when you are done with them.<br>
<br>
Lee<div><div></div><div class="h5"><br>
<br>
Jay Sprenkle wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Good afternoon all,<br>
<br>
<Newbie usage question alert><br>
<br>
After reading through the enet source it appears that when you send a packet of data a structure containing a pointer to the data is queued up to send. If I malloc() or new a buffer, fill it, then send it, how do I know when I can safely delete it? I don't see an event for sent data, etc.<br>
<br>
Thanks!<br>
<br>
</Newbie usage question alert><br>
</blockquote>
<br></div></div>
_______________________________________________<br>
ENet-discuss mailing list<br>
<a href="mailto:ENet-discuss@cubik.org" target="_blank">ENet-discuss@cubik.org</a><br>
<a href="http://lists.cubik.org/mailman/listinfo/enet-discuss" target="_blank">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><br>
</blockquote></div><br>