[Asterisk-Dev] MeetMe Improvement

[James Golovich]

I thought it was clear what I proposed, but I'll go over it.  Something
more like the iax.conf, sip.conf, etc. that has independant config
contexts for each entity.

We have 3 different types of config files now.  Heres my rundown on them:

- One Context inherited top down
The one used by zapata.conf, one context topdown where everything
inherits the config above unless overridden

- One entity per line
Then we have the one context with single lines representing entities,
these are not very scalable because you can only put so much information
on one line without making it confusing.  (voicemail.conf, agents.conf,
meetme.conf)

- One Context per entity 
Then there is the one context per entity method that I alluded to in my
previous email.  Of course there are downsides to everything, if
everything varies from the default the config file will be much larger,
but you can reorder the contexts and add/remove them without worrying what
will happen to the rest of the config

James

On Sat, 10 Jul 2004, Marc Olivier Chouinard wrote:

> What do you propose then ? 
> 
> -----Original Message-----
> From: asterisk-dev-admin at lists.digium.com
> [mailto:asterisk-dev-admin at lists.digium.com] On Behalf Of James Golovich
> Sent: Saturday, July 10, 2004 12:12 PM
> To: asterisk-dev at lists.digium.com
> Subject: Re: [Asterisk-Dev] MeetMe Improvement
> 
> 
> On Sat, 10 Jul 2004, Marc Olivier Chouinard wrote:
> 
> > Here is a sample of a future Conference app could look like. It 
> > support multiple user with different limit/pin for each users.  I 
> > based it on the zapata.conf with the channel setup, userid => create 
> > the user base on the lastest info he got from the previous entry.
> > 
> > I'll like your comment on it, should we look at another direction or ??? 
> 
> I don't think inheriting the above config entries is that great of an idea.
> I'd much rather see independant config contexts for each conference.
> 
> It's slightly easier to build config parser/generators that don't depend on
> specific order of entries, also for the newer users that type of config file
> can be difficult to wrap their brains around.
>