Thread: Winsock - Asynchrnonous Server problems

I'm messing around with asynchronous sockets, and I'd like to make a simple echo server. I have it setup all fine and people can connect and stuff, but when any client sends data to my server, I want the server to send back to every connected user, including the one that originally sent the data. I'm having a little trouble keeping track of clients and such with this problem. Has anyone ever made an asynchronous socket? I don't think I need to do multi-threading to solve this (I thought the idea of asynchronous was to eliminate multi-threaded socket stuff). Does anyone have an idea of how to set this up? Thanks.

I forgot to mention something else. The send() function takes a SOCKET as the first param. Is the socket the one that was created for listening? Or do I need to go through a loop of all connected sockets to use as the first parameter?

Have a read of this:
http://www.ecst.csuchico.edu/~beej/guide/

Have a read of this:
http://www.ecst.csuchico.edu/~beej/guide/

SOCKET is a typedef of type int, by the way, and I strongly recommend you explicitly use int instead of SOCKET, for portability.

Why?
Asynchronous sockets aren't available in *nix, right?

Thanks vVv for clarifying the first param. I'll add a reply with the results, whether they worked or not.

Oh, cool, I didn't know that. But at the moment, I'm not looking to make my software portable. It's mainly for personal use right now.

Are you utilizing asynchronous sockets with window notifications?

Yes, I'm using windows messages to use asynchronous sockets.