Configuration in a n-tire solution

  • Thread starter Thread starter =?iso-8859-1?B?UOVsIEY=?=
  • Start date Start date
?

=?iso-8859-1?B?UOVsIEY=?=

Hi,

My company are developing a framework (n-tire soulution) to use when we
are developing applications for our customers. Between the layers we
want to implement Web Services that serves the other layers (and other
applications) with the objects/data they need. I wonder if anybody have
an idee how to handle configuration? Idealistic we want to have only
one file/database to update when we need to do changes for our
customers.

Can someone give me a link to a article or something that describes how
other people have done this?

Or maybe you have done this, and want to share information with me.
Maybe you have used a dataset which gets it data from a database or
file? Or you have created an object that you have xml-serialized to a
file?
I really like to hear what you have done.

Pål
 
one good approach is to build your architecture so that configuration
settings are read from a configuration file that way you don't have to
recompile each time the database side changes. The configuration file can
simply point to a registry key for encryption purposes if you are not
comfortable putting passwords in a configuration file.

In that regard the services layer lies ontop of the database layer so that
direct access to the database is forbidden. This removes the burden of
connection strings etc from the developer and places it in the service
layer. This provides good abstraction. What sits on top of your service
layer is the logical tier et c etc

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006
-------------------------------------------------------



Hi,

My company are developing a framework (n-tire soulution) to use when we
are developing applications for our customers. Between the layers we
want to implement Web Services that serves the other layers (and other
applications) with the objects/data they need. I wonder if anybody have
an idee how to handle configuration? Idealistic we want to have only
one file/database to update when we need to do changes for our
customers.

Can someone give me a link to a article or something that describes how
other people have done this?

Or maybe you have done this, and want to share information with me.
Maybe you have used a dataset which gets it data from a database or
file? Or you have created an object that you have xml-serialized to a
file?
I really like to hear what you have done.

Pål
 
Back
Top