[ENet-discuss] ENet doesn't do servers?

[Shawn Yarbrough]

I must be missing something, but as far as I can tell, enet doesn't work for servers?

Some grepping of the ENet code base shows that the accept() system call is never called
anywhere.  (Unless the user calls enet_socket_accept() directly, which none of the
ENet instructions say is expected to ever happen.)

But the UNIX listen(2) man page says:

    To accept connections, a socket is first created with socket(2),
    a willingness to accept incoming connections and a queue limit
    for incoming connections are specified with listen(), and then
    the connections are accepted with accept(2).

ENet does call listen.  Then it polls/selects on the socket waiting for activity, but
when activity appears, it doesn't seem to do the right thing for a server which would
be to do an accept() system call.

If I could find one example of a working server, using ENet, it would probably help me.

Some ENet developer please correct me if I'm wrong, or please confirm that I'm right

and I'll help improve ENet to fix the problem.



Regards,

Shawn Yarbrough





      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.cubik.org/pipermail/enet-discuss/attachments/20071213/223cd52d/attachment.htm