WCF 4.0 ConcurrencyMode.Multiple and InstanceContextMode.Single Scalabiltity - wcf

I have a stateless WCF 4.0 (IIS 7.5) configured with
[ServiceBehavior(InstanceContextMode = InstanceContextMode.Single, ConcurrencyMode = ConcurrencyMode.Multiple)]
Question 1
Does InstanceContextMode.Single have any impact when configuring ConcurrencyMode.Multiple ?
Question 1
In order to have better Scalabiltity (hunders calls per second), should I change it to InstanceContextMode = InstanceContextMode.PerCall ?
Thanks

Related

WCF Throttling , InstanceContextMode and ConcurrencyMode

Which ConcurrencyMode and InstanceContextMode combination is best for WCF REST services considering heavy load?

Workflow 4 Service Application and InstanceContextMode & ConcurrencyMode

The question is pretty simple: how do you set InstanceContextMode & ConcurrencyMode in WF4 WCF Workflow Service Application?
You don't, they have no effect of workflow services.

How to make one WCF service to be client of another WCF service?

I'm not experienced WCF programmer, so I do not fully understand all those configs and endpoints.
I have made two WCF services. One is web service hosted in IIS7, and the other is Windows service.
What should i change in which app.config and web.config to make possible to IIS7 service be a client of Windows service. I have generated proxy for Win service imported in Web service, but I have no idea what to do with those app.config files... Can somebody give me general or concrete suggestions?
Thank you very much,
Regards,
A simple general suggestion. You can start with:
Client1 => Service1
Client2 => Service2
Once that working you can take the configuration from Client2 and copy it to Service1. Lastly you look at you Service1 as a client and do the same stuff you did for Client2 - add a service reference to Service2 (or get the proxy through another way if you will). Effectively, now your Service1 is also a Client2.
Client1 => Service1 => Client2 => Service2
WCF hosting doesn't matter here as services are communicating via ABC that is:
A - address (e.g. http://localhost:8080/Service1)
B - binding (e.g. BasicHttpBinding)
C - contract (e.g. IService1 interface)

WCF WebHttpServiceHostFactory vs. WebServiceHostFactory

What is the difference between WCF's WebHttpServiceHostFactory and WebServiceHostFactoryhosting?
Assuming that you're talking about the HttpServiceHostFactory from the new WCF Web API - http://wcf.codeplex.com/SourceControl/changeset/view/44d95f912edf#WCFWebApi%2fHttp%2fSrc%2fMicrosoft.ApplicationServer.Http%2fmicrosoft%2fApplicationServer%2fHttp%2fActivation%2fHttpServiceHostFactory.cs - this factory sets up the service / endpoint using the new HTTP pipeline for WCF (which is on codeplex). The WebServiceHostFactory sets up a service / endpoint using the "traditional" WCF REST style API (i.e., the one which was released with .NET Framework 3.5 and improved in 4.0).

wcf service start

I have a wcf service inside a windows service. Inside the wcf service I have a http listener which needs to be started automatically when the windows service is started. Any ideas?
Thanks for the answers but I found the solution
In order to have your constructor called, you need this:
[ServiceBehavior(InstanceContextMode = InstanceContextMode.Single, ConcurrencyMode = ConcurrencyMode.Single)]
can you not use IIS to host the WCF service, it has the WAS (Windows Activation Service ) to start the WCF Service?