Re: ResourceManager vs. ConfigurationManager
- From: "Yanir" <hexygen@xxxxxxxxx>
- Date: 15 Jul 2005 02:27:58 -0700
Thanks John,
but I tend to disagree about the performance issue.
First, the Configuration Application Block supports caching. Once the
file is initially loaded the data exists in memory for as long as the
application is alive. When talking about an ASP.NET application, the
loading of the file occurs only once for all users.
In that case I don't care if the loading takes a few seconds more.
Second, the Configuration Application Block supports storing the data
inside SQL Server. I presume loading a lot of strings from database
shouldn't be significantly slower then loading them from a compiled
resource file. Storing the information in database also seems easier to
maintain then a giant resource file.
Last, the Configuration Application Block supports storing of any user
defined object. I'm not sure if that's going to help me in this
specific case, but it seems more flexible than just storing strings.
I still see no pros in using the ResourceManager for that purpose.
Any ideas anyone?
Yanir
.
- References:
- ResourceManager vs. ConfigurationManager
- From: Yanir
- RE: ResourceManager vs. ConfigurationManager
- From: john conwell
- ResourceManager vs. ConfigurationManager
- Prev by Date: misleading error message - Config Section Handler
- Next by Date: Re: Adding domain user account to local administrator group
- Previous by thread: RE: ResourceManager vs. ConfigurationManager
- Next by thread: SerializationException with wrong dll version / PublicKeyToken
- Index(es):
Relevant Pages
|