[ENet-discuss] Two back-to-back send calls not allowed?

[Richard Becker]

It shouldn't over write the first message that makes no sense. The function is an abstraction and I am passing it the data to send not an eNet packet itself. Inside of the function a new packet is created and the data for the packet is set. I have debugged and traced all the way into enet_peer_send (which gets called from broadcast). Everything seems to be making it. I still dont understand why the client never receives the first message though and only the second one. Does this have something to do with enet internal queue for sending messages? Thanks - Richard
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cubik.org/pipermail/enet-discuss/attachments/20100811/e24794b6/attachment.html>