Don't use that WSAAsync stuff for non-blocking comms on Windows.
1. it's a headache to learn
2. it doesn't do async properly
3. the knowledge is non-transerable
4. Microsoft may one day realise it's nonsense and drop support for it
And also thanks for clearing up the select function, wasnt sure how to use it
( For anyone else who reads this... )
I also found it to be a parsing error, as when i did two send calls side by side, the 'buffer' received both and thus puts the two received strings next to each other. This means that i cant just parse a single message.