[asterisk-dev] Asterisk 11 configuration files
Tzafrir Cohen
tzafrir.cohen at xorcom.com
Mon Aug 27 17:44:51 CDT 2012
On Mon, Aug 27, 2012 at 11:42:42AM -0500, Matthew Jordan wrote:
>
> ----- Original Message -----
> > From: "Tilghman Lesher" <tilghman at meg.abyt.es>
> > To: "Asterisk Developers Mailing List" <asterisk-dev at lists.digium.com>
> > Sent: Monday, August 27, 2012 10:56:09 AM
> > Subject: Re: [asterisk-dev] Asterisk 11 configuration files
> >
> >
> > It's additionally worth noting that several modules have multiple
> > configuration file names, e.g. queues.conf & queuerules.conf,
> > sip.conf
> > & sip_notify.conf, iax.conf & iaxprov.conf. You cannot go with a
> > standard of naming configuration files based upon their module names
> > AND BE CONSISTENT, if some modules have more than one standard
> > configuration file.
> >
> > I agree with Leif, we probably shouldn't be naming configuration
> > files
> > by their module names, and this is just one more reason.
> >
>
> Playing devil's advocate here... what would happen if we did what
> Steve suggested and wrote a new voicemail module? Say, res_voicemail?
>
> There's a good chance that we'd want to get away from the configuration
> scheme that app_voicemail currently uses, i.e., defining voicemail
> user mailboxes as a single key/value pair. More likely, we'd want to
> use context templates to allow administrator's to define voicemail
> users. That radically changes how the voicemail configuration file is
> parsed and interpreted.
But what if we want to move app_voicemail.c to be res_voicemail.c (make
it a more reusable component). Will we have to rename the configuration
file just because we changed the name of a module?
And what if res_voicemail.c was eventually moved to main/ and became
part of the core?
--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.cohen at xorcom.com
+972-50-7952406 mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
More information about the asterisk-dev
mailing list