This isn't really about encapsulation vs. decoupling.
Encapsulation is about information hiding--keeping the details hidden,
decoupling is about separating a function into smaller pieces, generally for ease of reuse.
What you are talking about is configuration information that can be separated into two places.
This might, or might not be a good thing. It could be good if you, as the administrator want to
have sole control over the server operational parameters, but want to give someone else,
say a data administrator, the ability to update the welcome message without having to bother you.
This is a nice ability to have. Having multiple files comprise the configuration of the server
is not necessarily good or bad. It depends on how you want to manage the service.
Have fun,
Carl Forde
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
