wcf per-call, http-binding - idisposable pros cons

Question

1.00/5 (1 vote)

See more:

hello experts,

If I am using wcf service per-call mode and with http-binding
(not using multi-threading / thread in any method)
now If I implement IDisposible interface in my service
will there be any issue in performance?

Is it safe to implement IDisposible interface in this senerio?

I have done googling already but different-different articles makes me confuse.
so, if you can help I will be grateful.

Posted 14-May-14 19:33pm

Aarti Meswania

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)

m_sajid · Answer 1 · 2014-05-20T09:12:00

Solution 1

if your service is PerCall then why make things complex. keep it simple and let the hosting environment take care of your service instance lifetime.

Posted 20-May-14 9:12am

m_sajid