title: What is the correct way to handle long running service operations with WCF hosted in IIS?
body: <p>I am building a WCF service that will expose several operations, it will run in IIS because it needs HTTPS endpoints. Most of the operations will perform within seconds or less; however, one or two of these operations will take between 5-90 minutes.</p>
  
  <p>The primary consumer of this service will be an ASP.NET MVC application; what is the correct way to do handle this? </p>
  
  <p>Should I jackup the timeout and do some ajax calls? Should I add a table to my database, and have the long running operations update this database, and have the web interface poll this table every minute? I'm not sure what (if there is) the generally accepted best practice for this.</p>