[asterisk-dev] merging manager.conf and http.conf ?

[Matthew Rubenstein]

	No, there's no reason to merge those files. http.conf especially is
read infrequently, only when the httpd is restarted/reloaded, so the
extra overhead of a second file is negligible. And should we fork the
httpd source just so it reads the manager.conf for its configs, and
ignore the rest of the manager.conf Asterisk configs?

	Separate files that do specific things is the unix way, which after 35
years is the best way. What do we gain by merging them at that cost?


On Fri, 2006-10-06 at 03:19 -0700, asterisk-dev-request at lists.digium.com
wrote:
> Date: Fri, 6 Oct 2006 01:00:45 -0700
> From: Luigi Rizzo <rizzo at icir.org>
> Subject: [asterisk-dev] merging manager.conf and http.conf ?
> To: Asterisk Developers Mailing List <asterisk-dev at lists.digium.com>
> Message-ID: <20061006010045.A57041 at xorpc.icir.org>
> Content-Type: text/plain; charset=us-ascii
> 
> hi,
> in asterisk we have these two configuration files serving similar
> purposes - in particular, http.conf has very few options,
> and some features in manager.conf require things in http.conf
> to be enabled.
> 
> How about merging them into one (i suppose manager.conf is
> the one that should remain both for size and historical reasons) ?
> 
> cheers
> luigi 
-- 

(C) Matthew Rubenstein