On 12 January 2012 10:26, Tom Hobbs <tvho...@googlemail.com> wrote:
> I've no intention of removing or changing the interface, but we'll see what
> happens when I work out what to do.  I like Dan's convention over
> configuration plug.
>

Oh good ;)

There are various ways to achieve that of course. One would be for an
installer to generate the basic config using conventions and
auto-discovery. A similar thing could be used to construct a one-off
configuration each and every time one starts up.

Alternatively, one removes the need for reading configuration from a
file and can read one from memory with a set of conventions (or
auto-discovered defaults).

Perhaps we need a tweak to ServiceStarter that allows it to accept
start-up requests with no in-line configuration. We might have to
modify all the in-the-box services to follow one naming convention for
base configs so they can all be auto-configured from one source. That
or we change each service to auto-configure in absence of overrides.

Many ways to go, the key is to not need configuration by default...

> There's a number of improvements worthy of their own jiras mentioned on
> this tread.  I need to write them down before they get lost!
>
> Sent via mobile device, please forgive typos and spacing errors.
>
> On 12 Jan 2012 08:04, "Simon IJskes - QCG" <si...@qcg.nl> wrote:
>
>> On 11-01-12 15:49, Gregg Wonderly wrote:
>>
>>  The deal with ConfigurationFile, of course, is to be able to do
>>> configuration at deployment time, instead of at development time, and
>>> thus, even your development environment is a "deployment" that might be
>>> different from production. For example, in development, you might just
>>> use TCP endpoints, no policy, and a LUS group that is different from the
>>> production environment, so that there is no chance to interfere with
>>> production, which might be on the same routable/multicast-accessible
>>> network.
>>>
>>
>> So in order to keep this scenario in the future, we need to keep the
>> Configuration interface as the main interface to exchange the configuration
>> on. Agree?
>>
>> Gr. Sim
>>
>> --
>> QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
>> Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
>>

Reply via email to