@Robert Rudduck: What a great article! This discourages the use of the Session as a member variable and trusting to be clean inside one request. But if you allways use the session inside a using() statement, you should be save. There might even be the possibility with the member variable if you initialize it in OnLoad and dispose of it in OnPreRender, but thats a different story and doesnt change the unit of work concept. Im still reading the article, so there might be some new insight later on. For now, thanks!
Greetings! Zorgoban On 2 Mrz., 16:18, Robert Rudduck <[email protected]> wrote: > This link has a good explanation as well as experimental evidence: > > http://piers7.blogspot.com/2005/11/threadstatic-callcontext-and_02.html > > On Tue, Mar 2, 2010 at 8:28 AM, Angel Java Lopez <[email protected]>wrote: > > > Source link? > > > On Tue, Mar 2, 2010 at 11:10 AM, Fabio Maulo <[email protected]> wrote: > > >> because MS said that you may have more than one thread in a request. > > >> -- > > You received this message because you are subscribed to the Google Groups > > "nhusers" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<nhusers%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/nhusers?hl=en. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
