M
mabra
Hi !
I have a WCF [hosted in IIS], that has two methods, which both will be
called - one after the other - on a click by a ajax client. The first method
is
a method with long duration, the second method is a method with short
duration. Both calls terminate "at the same time". So, the call with the long
duration blocks the short call. Only one request from the same client can be
processed at the same time.
This is completely inacceptable. I added the interface
"IReadOnlySessionState" to the wcf service [no host declaration exists!!] and
used "ServiceBehavior(ConcurrencyMode=ConcurrencyMode.Multiple,
InstanceContextMode=InstanceContextMode.PerCall)". Nothing is of any help.
So, my resume:WCF is a bad decision to use with ajax.
If session handling on the asp(x) is disabled, everything works like
expected. But I need the seeion handling, so I tried the readonly attribute.
Oro I miss something????
Thanks a lot.
br--mabra
I have a WCF [hosted in IIS], that has two methods, which both will be
called - one after the other - on a click by a ajax client. The first method
is
a method with long duration, the second method is a method with short
duration. Both calls terminate "at the same time". So, the call with the long
duration blocks the short call. Only one request from the same client can be
processed at the same time.
This is completely inacceptable. I added the interface
"IReadOnlySessionState" to the wcf service [no host declaration exists!!] and
used "ServiceBehavior(ConcurrencyMode=ConcurrencyMode.Multiple,
InstanceContextMode=InstanceContextMode.PerCall)". Nothing is of any help.
So, my resume:WCF is a bad decision to use with ajax.
If session handling on the asp(x) is disabled, everything works like
expected. But I need the seeion handling, so I tried the readonly attribute.
Oro I miss something????
Thanks a lot.
br--mabra