Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Nov 30, 2012 06:03 PM by John Galt
Nov 29, 2012 06:49 PM|LINK
I have a case where I need to validate the values coming in, post them to the database, then return a success or failure to the end user.
I then need to continue processing some long running things that need to happen out of band (sending email, sms messages etc.) as a result of the API call (It's a post in this case)
Is there a way to to do this that is both scalable and doesn't kill the thread of the request without resorting to hacking another endpoint and calling it and not caring about the result?
Nov 30, 2012 04:35 AM|LINK
Could not get ur requirement completely, but it seems like you want to do tasks asynchronously like sending mails and messages,
well you have to create thread processes for that.
I have already given solution here, check it out:
Nov 30, 2012 06:03 PM|LINK
There's lots of threads saying this won't work because it will be killed as soon as the request is completed processing. I figured it would be even worse for Web API?