Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8820013
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 14, 20262026-06-14T05:30:18+00:00 2026-06-14T05:30:18+00:00

Suppose you have a WCF service with [ServiceBehavior( IncludeExceptionDetailInFaults = true, InstanceContextMode = InstanceContextMode.Single,

  • 0

Suppose you have a WCF service with

[ServiceBehavior(
    IncludeExceptionDetailInFaults = true, 
    InstanceContextMode = InstanceContextMode.Single,
    ConcurrencyMode = ConcurrencyMode.Multiple,
    UseSynchronizationContext = false)]

What difference does using the async/await pattern for service operations under this implementation make? Don’t the service calls get pooled and possibly executed asynchronously even if async/await is not used? Even after reading lots of msdn and blog articles, the above scenario is still not clear to me and I would asyncify my operations to be safe.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-14T05:30:19+00:00Added an answer on June 14, 2026 at 5:30 am

    Don’t the service calls get pooled and possibly executed asynchronously even if async/await is not used?

    No. ConcurrencyMode.Multiple will permit multiple threads to execute calls simultaneously, but that’s not the same as asynchronous processing.

    Consider a single synchronous request: a single thread will take the request and execute it all the way until it is complete. If that thread blocks, then you have a blocked thread waiting for that request to complete. You can specify ConcurrencyMode.Multiple to allow other threads to come in and do other calls without blocking on other requests.

    Now consider a single asynchronous request: a single thread will take the request and begin executing it. Instead of blocking, that thread will “await”, which returns the thread to the thread pool until the asynchronous operation completes. This means there is no blocking thread on that request. When the method resumes after its await, some thread from the thread pool will be used to continue the request (and eventually one of those threads will complete the request).

    The bottom line is that async on the server side allows greater scale than synchronous code, because asynchronous operations have lower overhead than threads.

    ConcurrencyMode deals with a different question: it’s about how threadsafe your service implementation is. If you can have multiple calls concurrently, you should specify ConcurrencyMode.Multiple. If you have naturally asynchronous operations, you should make them async. And if you’re threadsafe and naturally asynchronous, you should do both.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Suppose I have a wcf service listening on a remote server. Could a client,
Suppose I had a WCF service that I have coded up, like Clemens Vasters's
How to update WCF service reference dynamically in silverlight ? Suppose I have created
I have WCF service with IParameterInspector class which suppose to store the message for
Suppose i have following WCF Services. UtilityService (Service to provide utility functions) SomeOtherService 1
Suppose I have WCF web service that that can retrieve collection of <Person> objects.
Suppose I have a WCF service and a method in the contract <ServiceContract()> _
Lets suppose I have an .NET client application that connects to a WCF service,
Suppose I have a WCF service that is not session or singleton based and
suppose i have small wcf service which has duplex connection and i want that

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.