ThreadStaticAttribute and threadpool

[bruce barker]

a thread static will live the life of the thread. in asp.net, you are right,
there is a thread pool, with a min and max, so the life of a thread is hard
to predict. also asp.net plays fast and loose with its thread management, so
that there is no guarantee that the same thread is used for all of a page
processing. you can set aspcomat to true to force only one thread a page
request. you may want to context storage instead (say use application cache
which is context based) .

thread statics are only intialized once, so when the thread is pulled from
pool, the static will have the last value saved it in, so, you need to init
it every time.

-- bruce (sqlwork.com)

"Calvin" <szguoxz@hotmail.com> wrote in message
news:02c701c347dd$c49cc9e0$a301280a@phx.gbl...

> I assume every request is using a different thread, am I
> right?
>
> If a request is retriving a thread from a threadpool
> instead of creating a new thread (is this the case in
> IIS), what will happen to thread static variable?
> [threadstatic].
>
> I have applications depending on thread variable, I am not
> sure those thread static variable is resetted or not. And
> it's hard to test!
>
> Anyone has some inside knowlodge of this?
>
> Thanks,
>
> Calvin

[David Browne]

"Calvin" <szguoxz@hotmail.com> wrote in message
news:02c701c347dd$c49cc9e0$a301280a@phx.gbl...

> I assume every request is using a different thread, am I
> right?
>
> If a request is retriving a thread from a threadpool
> instead of creating a new thread (is this the case in
> IIS), what will happen to thread static variable?
> [threadstatic].
>
> I have applications depending on thread variable, I am not
> sure those thread static variable is resetted or not. And
> it's hard to test!
>
> Anyone has some inside knowlodge of this?
>

I think you might want to store your data in the Session,
instead of in a ThreadStatic variable.

David