[ENet-discuss] Connecting to self.

[Benoit Germain]

> -----Message d'origine-----
> [mailto:enet-discuss-bounces at cubik.org] De la part de Adam D. Moss
> Envoyé : mercredi 1 décembre 2004 17:45
> 
> Hi!
> I have a funny problem.  My app listens on a port and then 
> attempts to connect to itself (for testing purposes, for 
> now).  But this merely eventually causes a DISCONNECT 
> (presumably time-out) event, with no CONNECT.
> 
> However, if I launch a second process and do the connect from 
> there, the connection is fine.
> 
> Am I being stupid for attempting to have a process be a 
> client of its own server, or is there some unexpected 
> strangeness which prevents an ENet server from being its own client?

I have player with two hosts in the same application, with one connecting to
the other with no problem. But then, I have hacked the ENet core to be able
to specify the port I want the clients to use, so maybe things work
differently for me ?