Click here to Skip to main content
15,889,403 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Hello,

In our Web Application, We are using .Net Framework 4.0 with WCF Services.
We have a WCF Service with some DB operations after which
it generates a Report (Report Generation takes time).
Here user does not need to wait until the report gets generated and hence we have thought
of implementing Threading ( using System.Threading.Thread class and call this ReportGeneration in a new
Thread from the main thread immediately after DB operations are over).
Is it suggested to go ahead with Normal Threading or do we have a better approach ?

(Note :- We use .Net Framework 4.0 with WCF Services and WCF Service settings being set as InstanceContextMode = PerCall and ConcurrencyMode set to Single )

Please advise.

What I have tried:

Tried Implementing it using System.Threading.Thread and found it is working. But would like to know about the General Opinion on this approach.
Posted

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900