there are several levels of thread safe.
1) whether the code supports multiple threaded applications. all .net code
supports this, but not all c code.
then for objects:
2) can a object created on thread be accessed by another thread. (vb6 com
objects are an example where this can not be done safely).
3) if the object allows above, can two threads access it at the same time.
in the .net docs, this is what is meant by thread safe. some of the .net
runtime is, and some isn't.
for asp.net, #2 is required. the only exception is sta (vb6) com objects.
for sta com objects, aspcompat must be set. to handle this case asp.net
creates the com object on a single thread, and all calls are proxied (made)
from that thread.
-- bruce (sqlwork.com)
"jpatrcik" wrote:
Don't see any official notice that compiled library dll's loaded in the BIN
directory of an asp.net website need to be thread safe, but concurrent visits
to the same web site sure bear this out. Does anyone know the answer to this?