Possible alogrithms of handling 40 clients in a single udp server

Question

0.00/5 (No votes)

See more:

, +

I am working on udp server/cient application. I want my Server to be able to handle 40 clients at a time. Right now I am using the approach of creating one receiving thread which continuously receives data and one sending thread for sending data if required. Since the socket queue is large enough to buffer data from 40 clients so I am using only one receiving thread. What might be other possible ways to implement such single server multiple client application?

Posted 15-Apr-13 1:53am

ayesha hassan

Add a Solution

2 solutions

Solution 2

Your approach is reasonable. Keep the sending and receiving threads simple.

Use queues to buffer the data for the clients. Create a queue for each client. You could have a pool of threads, then processing incoming packets from those queues.

As CPallini mentions, you could create a seperate thread for each client.

The downside is that if your client threads need to do any heavy processing, they could miss packets. UDP doesn't gurantee delivery or have a mechanism to tell the sender to quit sending, that the queue is full...

Posted 15-Apr-13 11:47am

JackDingler

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)

CPallini · Accepted Answer · 2013-04-15T02:03:00

Solution 1

The other, quite obvious, approach would be creating a thread per client (well, two threads per client).
The adavantage would be a somewhat simpler code.

Posted 15-Apr-13 2:03am

CPallini

Comments

ayesha hassan 15-Apr-13 8:08am

For that do I need one main receiving thread and distribute the incoming clients on the basis of their IP addresses to specific threads?

CPallini 15-Apr-13 8:11am

Yes, that's the usual architecture of a multiple connections server.