Thanks Angus,
So you build your combobox, wait 10 seconds, one client disconnects, all
the clients numbers reduce by one and your combobox is out of date. When
you try to send a command to one of them it may be the wrong client or
you'll get an exception because there are fewer clients.
I didn't think of this :(
That's why you were told to use PeerAddr and PeerPort of the client, not
a client number, and look it up immediately before sending a command.
This I have been working on but I just can't success, that is why I have
been looking for an easier way.
Or more sensibly, look at the protocol I outlined in the my first message
a few days ago, which included the computer name in the packet fields,
then you can store that and use that instead (assuming your computers
have sensible names. You should be testing all this between multiple PCs
or VMs, as in real life, not 127.0.0.0 on a single PC.
Yes,
I am already testing in real life and even the clients are behind of another
network (not the same network).
I can't find the message you have sent with the computername in the packet
fields.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
