Reply to thread

Message

[QUOTE="bruce barker \(sqlwork.com\), post: 527835"]
you need to setup a background thread to do this. this is because of the
page life cycle.

1. at the start of the request a thread is selected from the pool.
2. a new instance of the page is created
3. the page lifecycle methods are called
4. the request is sent back to the iis.
5. the thread is return to the pool.

it a litle more complicated, as the thread may be returned to the pool and
new one selected during page lifecycle processing.

as you can see, when your delegate fires, the thread that started the async
request may be in the pool, destroyed, or processing the next page request.

if your site has light load,  you can create a new thread everytime, if not,
you proably want one background thread, or a pool, created as needed. then
use a queue to send work to it.

note: the new thread will run as the asp.net account, not the account of the
thread creating it, so you may need to do some impersonation.

-- bruce (sqlwork.com)
[/QUOTE]

Verification