I can. In fact, that's what I'm doing. But I don't want to incur another send, hence the piggybacking question.
Another unrelated question is the following: I have 2 servers, I want to establish only one connection between the two. Right now, I have to essentially make sure that only one initiate the connection. That implies that I have to have separate logic for the server that initiate the connection. But these are really the same servers, is there a simple way guarantee only establish one connection between the two when I allow each each server to attempt to connect to the other? On Wed, Mar 31, 2010 at 10:00 AM, Jay Sprenkle <[email protected]> wrote: > Why don't you send a packet to identify the process that is connecting? > > > > On Wed, Mar 31, 2010 at 10:00 AM, benchmark <[email protected]> wrote: > >> is there a way to piggyback some data (an 16bytes server id) on connect, >> so that the target knows who has connected? I want to pass the client's id >> to the server, in addition to its host/ip that's part of the peer info. >> > > > -- > --- > I couldn't have said it better myself: > "Hitler and cloud computing" > http://www.youtube.com/watch?v=VjfaCoA2sQk > > > _______________________________________________ > ENet-discuss mailing list > [email protected] > http://lists.cubik.org/mailman/listinfo/enet-discuss > >
_______________________________________________ ENet-discuss mailing list [email protected] http://lists.cubik.org/mailman/listinfo/enet-discuss
