Hello,
is there any news about this problem?
Me, too, would need to have ConcurrencyMode.Multiple (or
InstanceContextMode.PerCall), with a WebHttpBinding. I tried it, it does not
seem to work. Can anyone confirm that MONO does not support this?
Thanks.
--
View this message in context:
I can't give a definite answer, but at least the throttling limitation
will go away ;-)
Atsushi Eno
(2010/11/22 15:41), Chakotey STME wrote:
hello,
thanks for your answer.
That's correct. I am using mono 2.6
If I change to mono 2.8 - will die clients run parallel?
chakoteystme
So I have to test it with using a mono 2.8 installation?
chakoteystme
2010/11/22 Atsushi Eno atsushi...@veritas-vos-liberabit.com:
I can't give a definite answer, but at least the throttling limitation will
go away ;-)
Atsushi Eno
(2010/11/22 15:41), Chakotey STME wrote:
hello,
thanks
Hello,
Not sure what is exactly happening, but if you are using mono 2.6 then I
limited service throttling the maximum concurrent sessions (and thus
calls) to 1 for stable processing (and you cannot change it through
ServiceThrottlingBehavior, as it is hard coded). So you won't get two
hello,
thanks for your answer.
That's correct. I am using mono 2.6
If I change to mono 2.8 - will die clients run parallel?
chakoteystme
2010/11/22 Atsushi Eno atsushi...@veritas-vos-liberabit.com:
Hello,
Not sure what is exactly happening, but if you are using mono 2.6 then I
limited
Hello,
I have a problem with WCF.
I have a service:
ServiceBehavior(ConcurrencyMode:=ServiceModel.ConcurrencyMode.Multiple,
InstanceContextMode:=InstanceContextMode.Single) _
Public Class HelloService
Implements IHelloService
Private Shared thisInstance As HelloService
Protected Sub