Threading advice & question

Question

0.00/5 (No votes)

See more:

.NET4.6

I have a website that goes out and queries/consumes 12 different Webservices. Some are SOAP, some URL-REST. Right now the code is set up like a Rolodex, as one Webservice result is returned the next request is fired off. Been reading up on threads and am wondering if this is a good way to go with consuming Web services or is there another avenue I should look at. Webservice results are usually pretty fast but the way the site is working now If one webservice is slow or down it slows the whole process down. If I go to use of threads my main concern is how do know when the treads are finished individually so I can process and display all the results.

Thank You.

What I have tried:

just starting out and looking into threads. Need advice or direction.

Posted 5-Aug-19 7:30am

danash

Updated 5-Aug-19 10:44am

Add a Solution

3 solutions

Solution 3

Use tasks (System.Threading.Tasks) instead of threads, that way you won't necessarily even allocate a thread for an operation.

For example, a lot of your services are IO bound - waiting for HTTP request response cycles.

You can do a kernel wait on that, suspending it, and running other code without creating a separate thread. (Windows handles it internally, through IOCP and .NET gives you the ability to use it via tasks)

You don't need to worry about it if you do it this way in a server application, generally. If you're already scaling well with your synchronous model this way should be great for you.

Rick Zeeland posted first so accept his if you were to accept either of ours, but I wanted to give you a little bit of background on tasks

Posted 5-Aug-19 10:29am

honey the codewitch

Solution 4

Add callbacks for each service's "completed" event. Start all services.

In each callback, set an indicator that that service has completed. At the same time, check all other "service" indicators. When all indicators are set, all services have run, and the last callback can trigger the "all completed" event.

How to: Call WCF Service Operations Asynchronously | Microsoft Docs[^]

Posted 5-Aug-19 10:44am

Gerry Schmitz

Updated 5-Aug-19 10:52am

v3

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)

RickZeeland · Accepted Answer · 2019-08-05T08:12:00

The modern (and recommended) way of doing things is using Tasks, see: Task Class (System.Threading.Tasks) | Microsoft Docs[^]
If you want to know what is so great about Tasks, read this series of CodeProject articles:
Task Parallel Library: 1 of n[^]

You can use Task.IsCompleted to check if a task is finished.