basically I have a custom class that is a configuration section handler. It reads all of the settings for the config file and exposes such properties as static-read only properties that can be used anytime throughout the amsi application. In my security framework, I have an abstract factory interface for different providers and 2 concrete factory classes implementing the interface (sql and directory services). The methods in the factory are class creation methods (IUsers CreateUsersDA(), IRoles CreateRolesDA(), etc...). What I would like to do is encapsulate the logic for determining what concrete factory to instantiate inside the configuration section handler class and expose it via a static property. My concerns are: * are there any potential concurrency issues that I would need to be aware of (would the static property need to use a read-only lock)? * are there any performance issues resulting from this technique?
All comments are appreciated...thanks, _howard You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
