I'll use a bunch of events, and get notification for the sockets. Then I'll have a few worker threads running and handling events. I don't know if that'll work, but it has to be easier than IOCP and probably quite close to as efficient. If it starts to become a problem, I can look at IOCP again later on. This is the second time I've got a pretty much completely implemented IOCP socket class, and had to give up. I'm sure there's something I'm missing.
At the moment, I just want to get the socket code done so I can work on the rest of TEH MMORPG!!1 (I'm calling it a MMORPG, even if it's just a MORPG).
I realised something slightly annoying about setting up my laptop to do coding on the train last night: How do I sync files? I'll have to remember to do it in the morning, and when I get home. It shouldn't be too bad actually, I only tend to do my own coding for part of my lunch break and on the train (soon) during the week. So in theory I could leave files checked out for 5 days, although I'd rather not (The more often I commit, the more versions I have to go back and check on).