Re: [Yxa-devel] Using YXA's stack

2008-07-31 Thread Fredrik Thulin
Evgeniy Khramtsov wrote: > Fredrik Thulin wrote: > >> Because it doesn't let the application perform validation, >> normalization etc. on the configuration data and it is unknown if >> entering something looking sensible (uhh) e.g. : >> >> {ssl, [{protocol_versions, sslv3}]} >> >> will have an

Re: [Yxa-devel] Using YXA's stack

2008-07-31 Thread Evgeniy Khramtsov
Fredrik Thulin wrote: > Because it doesn't let the application perform validation, > normalization etc. on the configuration data and it is unknown if > entering something looking sensible (uhh) e.g. : > > {ssl, [{protocol_versions, sslv3}]} > > will have any effect at all, or there was in fac

Re: [Yxa-devel] Using YXA's stack

2008-07-31 Thread Fredrik Thulin
Vance Shipley wrote: > On Thu, Jul 31, 2008 at 12:46:55PM +0200, Fredrik Thulin wrote: > } I'm not very fond of the application environment anymore. > > Why not? It's the OTP way. Because it doesn't let the application perform validation, normalization etc. on the configuration data and it is

Re: [Yxa-devel] Using YXA's stack

2008-07-31 Thread Vance Shipley
On Thu, Jul 31, 2008 at 12:46:55PM +0200, Fredrik Thulin wrote: } I'm not very fond of the application environment anymore. Why not? It's the OTP way. -Vance ___ Yxa-devel mailing list Yxa-devel@lists.su.se https://lists.su.se/mailman/listinfo

Re: [Yxa-devel] Using YXA's stack

2008-07-31 Thread Evgeniy Khramtsov
Fredrik Thulin wrote: > You could very well have the above snippet in your local_xxx.erl file > though, if we add a hook to retrieve configuration backends. A hook is > appealing since it allows everyone to solve the problem anyway they > like (hardcode, os:env variable, your way, ...). > Ah, o

Re: [Yxa-devel] Using YXA's stack

2008-07-31 Thread Fredrik Thulin
Evgeniy Khramtsov wrote: > Fredrik Thulin wrote: > >> If you make your AppModule:init/0 return MnesiaTables 'none', >> sipserver:init_mnesia/1 should not do anything harmful, or does this >> have some other drawback to you? > > sipserver:init_mnesia(none) calls table_update:update(), which fail

Re: [Yxa-devel] Using YXA's stack

2008-07-31 Thread Evgeniy Khramtsov
Fredrik Thulin wrote: > If you make your AppModule:init/0 return MnesiaTables 'none', > sipserver:init_mnesia/1 should not do anything harmful, or does this > have some other drawback to you? sipserver:init_mnesia(none) calls table_update:update(), which fails with reason {aborted,{no_exists,{

Re: [Yxa-devel] Using YXA's stack

2008-07-29 Thread Fredrik Thulin
Evgeniy Khramtsov wrote: > Hello! > > 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, Thanks! > but I have some questions and proposals. > 1. When YXA application starts, it passes MnesiaTables to