
Signature
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Thanks for the reply Luke. The following response was posted over on the
framework.aspnet group, and is probably more applicable to what I'm dealing
with.. You mentioned a connection object in your post, but my case has
really nothing to do with a connection object. In my particular scenario,
I'm concerned about static methods passing non-static collections out, and
according to Paul's post, it seems these should be just fine. If you care to
add comments on Paul's post that couldn't hurt, but I think I'm seeing
things clearly now..
Thanks again,
S
"Paul Glavich [MVP - ASP.NET]" <glav@aspalliance.com-NOSPAM> wrote in
message news:<eV2FQN4KEHA.892@TK2MSFTNGP09.phx.gbl>...
> You are ok as long as nothing is shared. The collections you
> mentioined, while created/modified in a static method, are in fact
> created on the heap as per normal and although the same method can be
> accessed by multiple users (static method), the variables it creates
> are specific heap instances and therefore not shared across any static
> methods unless they themselves are static or thread statics. The DAAB
> (Data Access Application block) is based on this premise.
> So basically dont worry. All is good.
> --
> - Paul Glavich
> Microsoft MVP - ASP.NET
> The returned connection object fromt the static method is not
> static/shared. Generally, it is thread safe if the collection object is
[quoted text clipped - 8 lines]
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)