[ENet-discuss] client get disconnected after 52 seconds

[tom m]

Hi Jonathan,
 Thank you very much. You are completely right!!!
 I was using only enet_host_flush in my client. 
 So now I have added a enet_host_service in my client and it is working perfectly.
 Thank you again for your help and your fast reply,
 
 Tom.

LoneSock <lonesock at gmail.com> wrote: Hi.
 
 By any chance are you only sending packets with "enet_host_flush"?  I believe that if you use only that function and never use "enet_host_service", then your client will not respond to the automatic keep-alive packets.  Try using enet_host_service in your client's main loop (at least every few seconds).
 
 Jonathan
 
 

On 11/21/05, tom m <email_4_forums at yahoo.com> wrote: Hi,
 I first want to thank you for this library.
 
 I have a client/server architecture.
 When I create a client peer which is only sending packets to the server, it gets disconnected after approximately 52 seconds. 
 Therefore, my Server (peer) receives an ENET_EVENT_TYPE_DISCONNECT after 52 sec.
 So the application is working fine for 52 sec and then I have to restart it.
 The server is only receiving the packets and processing them. 
 
 Any ideas?
 I am using the code from the tutorial.
 Thanks for your helps,
 
 T.
 
 
 
   

---------------------------------
  Yahoo! FareChase - Search multiple travel sites in one click.       

_______________________________________________
ENet-discuss mailing list
ENet-discuss at cubik.org
 http://lists.cubik.org/mailman/listinfo/enet-discuss



 


-- 
Piranha are people too. _______________________________________________
ENet-discuss mailing list
ENet-discuss at cubik.org
http://lists.cubik.org/mailman/listinfo/enet-discuss



		
---------------------------------
 Yahoo! FareChase - Search multiple travel sites in one click.  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.puremagic.com/pipermail/enet-discuss/attachments/20051122/43ed2e90/attachment.htm