By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,963 Members | 1,902 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,963 IT Pros & Developers. It's quick & easy.

Multithreading Async aspx best approach

P: n/a
I've spent the last 3 hours reading various MSDN articles, other site
articles and news group postings and was wondering what the best approach to
my situation would be since I'm unable to come up with the best approach.

What's Needed........
1. Various background SQL inserts that don't interrupt the client
request/response
2. Various background emails generated and sent that are separate from the
client request/response
3. Every single page load doing a SQL insert that is separate from the
client request/response
4. And other similar tasks........

Also, my site is running MSCMS 2002. Now, should I put all this background
processing code in a separate dll that can be called from the application
state? Or, put code in a separate dl that can be called from anywhere as
needed? And, what would be the best approach........

Async Handler with custom thread pool below seems like overkill, isn't their
a much easier way?
http://msdn.microsoft.com/msdnmag/is.../06/Threading/


--
Marc Miles
Nov 18 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
I'd suggest creating a Windows Service to handle all your background tasks.
Here's more information on Windows Services:
http://msdn.microsoft.com/library/de...owsService.asp

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net
"milesm" <mi****@u.washington.edu> wrote in message
news:c7***********@nntp6.u.washington.edu...
I've spent the last 3 hours reading various MSDN articles, other site
articles and news group postings and was wondering what the best approach to my situation would be since I'm unable to come up with the best approach.

What's Needed........
1. Various background SQL inserts that don't interrupt the client
request/response
2. Various background emails generated and sent that are separate from the
client request/response
3. Every single page load doing a SQL insert that is separate from the
client request/response
4. And other similar tasks........

Also, my site is running MSCMS 2002. Now, should I put all this background processing code in a separate dll that can be called from the application
state? Or, put code in a separate dl that can be called from anywhere as
needed? And, what would be the best approach........

Async Handler with custom thread pool below seems like overkill, isn't their a much easier way?
http://msdn.microsoft.com/msdnmag/is.../06/Threading/


--
Marc Miles

Nov 18 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.