[Asterisk-doc] modules instead of config-files

[Martin List-Petersen]

Citat Leif Madsen <leif.madsen@gmail.com>:

> > As I have expressed earlier, I feel that describing channel,
> > application, etc. and their related config files is the better way to
> > go, since one channel driver can have more than one configuration file
> > and you usually want to configure one service and everything that is
> > related to it.
> 
> I have just read through most of your changes, and I really like where
> you are heading with this.  It still looks to be a rough draft (but
> which sections are not...), but I would say we should move towards
> this style.
> 
> I agree with you that saying the channel, application etc... and then
> the configuration files associated with that makes sense.  This allows
> us to make it easier to search for a specific part of configuration. 
> If we are only interested in a certain channel, then we can find it in
> chapter 6 and only have to bother reading the configuration changes in
> the files associated with that.  This way we don't have to try and
> explain "everything" about zapata.conf in one spot, we can have
> zapata.conf in a couple of spots relating to different channels,
> drivers, applications (as an example).

That is exactly the intention. Some parts, like chapter 6, will be used for
reference when configuring stuff. Often you will sit with the box and just need
all the information you can get about that one specific channel.

> Good work!  I'd say you can probably check this into CVS, but I'd like
> to hear opinions from other people as well (Jared and Jim, I'm looking
> in your direction :D)

I'm holding off to submit it until then. 

/Martin
-- 
Never raise your hand to your children -- it leaves your midsection
unprotected.
		-- Robert Orben