Thread Safety in calling Business->Foundational Modules

Topics: Web Client Software Factory, User Forum
Sep 4, 2007 at 10:55 PM
Edited Sep 4, 2007 at 11:27 PM

In our WCSF solution, we have a business module which in turn calls a foundational module -
When the ASP.NET page calls the business module, the createnew attribute ensures that we get a new presenter for each worker thread. I assume this would be enough to handle business module thread safety.

Would the same cover foundational modules? Wont foundational modules behave like plain DLL calls outside ASP.NET and hence, can have potentially multiple worker threads calling the same dll ?

Do we see any issues of thread safety if we save user specific information in plain DLL's (Foundational modules) ?

Any insight is appreciated -

Sep 5, 2007 at 7:31 PM
I believe that anything you're registering in any Service collection will be Singleton and therefore will need to be written thread-safe. If you're just using Dependency Injection then those objects are not Singleton.