Re: Why I cannot use tuple as application env key?

Max Lapshin <[email protected]>
Newsgroups gmane.comp.lang.erlang.general
Message-ID <CAMxVRxA3Fe0MTGpRsHyr=Hn7M8-qgWFALMNu0Zmc9yODa7DmOw@mail.gmail.com>
You can try to use persistent option and will see that it doesn't work.

On Wed, Oct 28, 2020 at 1:37 PM bengt <[email protected]> wrote:
>
> Greetings,
>
> I use application:get_env only once (in application callback module during start/2), to move config from application env to where it is used.
> At this time it is possible to change layout/keys as much as needed.
>
> Doing it repeatedly was not something I considered in my suggestion. Sorry.
>
> Best Wishes,
> bengt
>
> > On 27 Oct 2020, at 08:11, Max Lapshin <[email protected]> wrote:
> >
> >> The key is documented as being atom. Unfortunately why is not documented.
> >>
> >
> > Yes, and there is a simple check in application_controller that
> > disallow anything except atom.
> >
> >> {backend, [{Name, Configuration}]}
> >
> > This will give me full proplist on each access.  I have tried it with
> > thousand of elements and found that GC is going mad on high traffic.
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.