I already asked this here before and got no answer, but I was able to get it working, forcing the client to send a packet on connection. When the client sends the packet, the server will receive the connection event, but I was not able to make the server actually read that packet contents.
<br><br>If you get it working, please PM me about your solution.<br><br><br><div class="gmail_quote">On Dec 13, 2007 10:44 AM, Shawn Yarbrough <<a href="mailto:shawnyar217@yahoo.com">shawnyar217@yahoo.com</a>> wrote:
<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div style="font-family: courier,monaco,monospace,sans-serif; font-size: 12pt;"><div>
Hi,<br><br>This is my first try with ENet, enet-1.1 stable release, on Linux.<br><br>My client-server ENet test programs aren't working as expected. The client connects to the server and sees a connection event, but the server never sees the connection event.
<br><br>I've included sample runs and code below. If I'm doing something boneheaded, I was hoping somebody could point out my mistake.<br><br>Also I was looking thru the ENet source code trying to understand it. It looks like the UNIX accept() function is never called, or actually it is called by enet_socket_accept(), but then enet_socket_accept() is never called. I assume I'm missing something. I'm not supposed to call the ENet socket functions myself, am I? The tutorial doesn't mention them at
all.<br><br>Regards,<br><br>Shawn Yarbrough<br></div></div></div></blockquote></div><br><br clear="all"><br>-- <br><a href="http://danny.bitcrafters.com.br/">http://danny.bitcrafters.com.br/</a><br><br>Animal Liberation Frontline.
<br>Art.32 Lei Federal 9.605/98.