look for errors coming with FD_CONNECT message, look for FD_CLOSE
message, and inform relay when connection is lost so its reconnect
logic is triggered. This seems at least to handle the case where I
kill the relay mid-game.
read/writer, to provide connection status beside scoreboard (in area
outside that managed by code in common/). Simple letters now, it'll
be icons eventually.
socket-writable and on receiving message to be sent; cleanup. With
this change full robot-vs-robot game has worked over relay, but not
reliably. I think it's the relay's fault. Still tested only on Win32.
replacing dedicated threads for read and write with non-blocking
sockets driven from the main window proc. So far it can do a
round-trip against the relay on win32, and compiles but isn't tested
on wince.
that win32 build can open games saved by previous version, but nothing
else (e.g. use of network or even dialogs to set up relay connection
parameters.)
connType and adding choice how to connect. Bt connect dialog is
invoked, but the fields won't be populated. Pass conn type into
socket constructor, assuming socket code doesn't change much to use BT
rather than TCP.
threads, reader and writer, on a single socket. With this checkin a
connect request reaches the relay and a response comes back and is
passed to and recognized by the common code. A full game should now
work, but hasn't been tried. Nor is there any handling of socket
errors, retries, etc.
