<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2800.1226" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Hello, this is my first time posting to enet. First off,
just want to add that ENet is definite gem of a find and much appreciated.
I downloaded the latest source from about 1 week ago and integrated the library
into our application. I have a thread that calls enet_host_service()
approximately every 100ms with a mutex so that the enet_host_service() calls
won't overlap the enet_peer_send() calls (some coarse grained multithread
support). We then proceed to send RELIABLE packets with no problems.
However, we notice that our large packets (approx. 1500 bytes) are not making it
through. After a little investigation I can confirm that this behaviour
coincides with our crossing of the single fragment barrier. I also
confirmed that all the data seems to be sending properly from the peer and is,
indeed, being received by the host (at the socket layer). This leads to me
be believe the issue is somewhere in the fragment reassembly code. This is
assuming that I haven't missed something very simple regarding large packet
sizes and ENet.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>I am doing this on WinXP using MSVC 6. Any insights that
might point me the right direction or perhaps some references to specific
lines of code that I could watch would be greatly appreciated.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>thanks,</FONT></DIV>
<DIV><FONT size=2>Pete Diemert</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV></BODY></HTML>