Slightly confused about Asynchronous Sockets (Client)

Question

4.00/5 (1 vote)

See more:

Hello,

I coded an application which purpose is to continually exchange data with server. However I would like to have more connections established in this process. Like 10 connections from one process to the server at the same time.

I still doesn't see the concept behind asynchronous handling:

I would like to have it like this ->

CConnection connections[10];

and somewhere handling the receive like this ->

"If I'm ready to receive, then receive data and pass it to currently selected connection."
Like: connections[selected]->HandleRecv(bRecievedData);

Could someone please explain me how to achieve such goal?

Thank you

Posted 17-Mar-11 9:18am

Im2N00By

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Espen Harlinn · Accepted Answer · 2011-03-17T10:15:00

Solution 1

Download and stydy Echoc.exe - Simple Overlapped Socket Client Sample
http://support.microsoft.com/kb/193066[^]

Regards
Espen Harlinn

Posted 17-Mar-11 10:15am

Espen Harlinn

Comments

Sergey Alexandrovich Kryukov 18-Mar-11 15:17pm

Interesting work referenced, should help, my 5.
--SA

Espen Harlinn 21-Mar-11 12:40pm

Thank you, SAKryukov!

Im2N00By 19-Mar-11 15:22pm

It's little bit more clear now. I will try it with MFC CAsyncSocket for now until I will understand it little bit better.

Thank you

Sergey Alexandrovich Kryukov 20-Mar-11 23:09pm

I would prefer using sync. sockets (all blocking calls) with threads.
--SA

Espen Harlinn 21-Mar-11 12:43pm

For a large number "low-traffic" of concurrent users - asynch may provide better performance, while synch sockets are usually easier to implement, and often offers better performance for scenarios involving "few" concurrent users and a lot of traffic.

Sergey Alexandrovich Kryukov 21-Mar-11 23:26pm

One more note in favor of the sync. sockets: an unlimited number of users can be served with fixed number of threads. A thread per sockets is a really crazy idea when number of connections can grow unpredictably.

(You know, I once come across the whole Internet community of opponents of... threading. They maintain threading is evil. Arguments? In introductory article a patient explains how he created a service using a thread per socket, it "worked fine" before it was open for production... No wonder. Very nice argument: using some idea in idiotic way and argue the idea was idiotic...)

--SA