Maintain state during the long synchronous requestresponse process in WCF

Question

0.00/5 (No votes)

See more:

Hi All experts,

I am a bit new to WCF. I had explicit requirement to prepare a wcf application with below requiements,

1. Need to prepare synchronous WCF service hosted in IIS
2. Client will consume synchronous WCF service.
3. request & response might take long time, as other applications are involved in this process.
4. Need to maintain the state during this long request & response process.
5. Should not use any Workflows

So basically, I need to maintain state without lossing/deadlocks during the long synchronous request<->response process.

Please share your valuable suggestion.

Regards
balu

Posted 11-Feb-13 7:02am

balu12345

Add a Solution

1 solution

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)

P_Dash · Answer 1 · 2013-02-11T07:36:00

Yeah, requirements like this comes in case of Services which depend on multiple resources.

I'd suggest you the following points, implementing which you could achieve your desired result:
1-In ServiceContract use the following SessionMode attribute:

C#

[ServiceContract(SessionMode=SessionMode.Required)]

2-In ServiceBehaviour use PerSession attribute as following:

C#

[ServiceBehaviour(InstanceContextMode=InstanceContextMode.PerSession)]

3-And since you are saying that multiple applications are involved in this Service, so use Reentrant property of Concurrency in ServiceBehaviour as following:

C#

[ServiceBehaviour(ConcurrencyMode=ConcurrencyMode.Reentrant)]

This will help you to avoid any kind of DeadLock.

I'm sure if you could use the above properties efficiently then you would surely achieve your desired goal.

Regards,
Gittu