I'm working on SIP gateway to a foreign protocol network and I'm using 
YXA's SIP stack for that. All works fine, YXA is a realy amazing thing, 
but I have some questions and proposals.

1. When YXA application starts, it passes MnesiaTables to sipserver.erl, 
which calls init_mnesia(MnesiaTables). However, I don't want to 
initialize all that YXA's mnesia stuff since I'm using my own mnesia 
initialization and mnesia tables. So, my proposal is to define 
"init_mnesia(undefined) -> ok;" in sipserver.erl, and to fix 
yxa_monitor.erl slightly to make it able to understand 
{add_mnesia_tables, undefined} message.

2. As I can understand, it is not possible to add another config backend 
without changing YXA's code directly becase ?BACKENDS are hardcoded in 
yxa_config.erl. This is not really good for me since I want to use my 
own configuration file :(. Maybe I misread something and it is possible 
to change config backends in runtime?

3. Looks like YXA's config parser fails if it sees unknown variable 
without "local_" prefix. I wonder if it is possible to avoid such 
behaviour, because I don't to add "local_" prefixes to my configuration 


Evgeniy Khramtsov, ProcessOne.

Yxa-devel mailing list

Reply via email to