Stanley,
Any lengthy process on a web page will eventually run afoul of the
execution timeout. If I need to handle a lengthy process then I tend to
hand it off to a Windows Service via .NET remoting -- it could be on the
web server, or on a different machine. Your UI can then go do other
things and you can have a way for the user to check on the progress of
queued tasks, or simply have the service email the user on task
completion. Or you can sit on a page with some kind of animation to
illustrate the passage of time, and have the page refresh every 15
seconds or so and check if the task is done. Something of that nature.
If you are sending a lot of emails you might want to look at
www.jangomail.com. They have a terrific web engine for sending out
email broadcasts in a professional manner, handle bounces, etc. And
they have a web services API that you can talk directly to in order to
pass addresses in, execute mailings, etc. Also they have a terrific
browser-based authoring system for creating emails, including spam
scoring and the like. You can set things up so that emails come from
your own subdomain with proper traceability back to you, etc. Basically
they have all the pieces for distributing email broadcasts of arbitrary
size, and the pieces are all customizable in various ways. You have to
be prepared to do things professionally, spammers are not welcome.
--Bob
Stanley Cheung wrote:
Hi all,
I am developing the application for send emailing list,
actually, i can perform to send a email 1 by 1 and do it on aspx page.
I have a enquiry that how can the application change to background task
instead of user need to wait and wait until all email sent.
Also, when user waiting to complete the emailing list, the page is blank and
nothing, can we put a layout when user waiting a request.
Thanks.
steambun