[erlang-questions] sharing config via a dynamically compiled module?

Ilya Khaprov ilya.khaprov@REDACTED
Sat Oct 28 08:06:51 CEST 2017


I did this, feels good.
If this is for config,  I would say use config_change and regen.
Also code:delete/1 and code:purge/1.


From: Benoit Chesneau<mailto:bchesneau@REDACTED>
Sent: Wednesday, October 25, 2017 03:29 PM
To: Erlang Questions<mailto:erlang-questions@REDACTED>
Subject: [erlang-questions] sharing config via a dynamically compiled module?

I'm temped to compile dynamically a module for some highly demanded resources
to share their config instead of using ETS for it. But I'm wondering if's not
to hackish. (I'm also tempted by just using something more pure like sharing it
via message passing).

Are other people do such thing? I can see the following pro/cons:


    * fast and constant access, it is just a call to a module function and some literals.


    * maybe too much hackish?
    * What happen if the resource is deleted when someone is using it? Will the
      module be really deleted or will it leaks?

What do you think about it? Any feedback is welcome :)

- benoît
erlang-questions mailing list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20171028/696705eb/attachment.htm>

More information about the erlang-questions mailing list