Difference between Multi-threaded socket server & Non-blocking socket server?

Question

2.00/5 (1 vote)

See more:

Hello everyone,

I'm now programming a socket server for my applications' communications. I want my threading pattern to implement a server that can allow multiple requests at the same time (not waiting as a sequential queue does). I've come across the Blocking property too. What's different between these two?

Thanks!

Posted 25-Mar-10 2:44am

Neonamu

Updated 25-Mar-10 6:16am

Sandeep Mewara

v3

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)

Mustafa Ismail Mustafa · Accepted Answer · 2010-03-25T05:41:00

Primarily, the difference between a multithreaded socket server and a non-blocking is pretty subtle.

In both cases, multi-threading is involved. The main difference lies in the handling of the request.

In a Multi-threaded server, once a request is received, the rest of the operation(s) which include everything from transferring data to processing is then thrown to another thread which takes it from there and handles all of the work and finally closes the connection (hopefully in a graceful manner).

A non-blocking server has one thread that listens on the port and when a request is made it then delegates a specific task to a "background" thread so that operation of that thread can continue and not be blocked by a long running (possibly failing) function.

Did that explain it well enough?