<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.5659" name=GENERATOR></HEAD>
<BODY>
<DIV>
<DIV>Hello,</DIV>
<DIV> </DIV>
<DIV>I asked myself the same question.</DIV>
<DIV> </DIV>
<DIV>I read the source code of the application_controller module, the
get_env function use access to the local ETS table "ac_tab".</DIV>
<DIV> </DIV>
<DIV>From a performance point of view, I don't think that it's a problem. </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>wde</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV></DIV>
<DIV>
<HR>
Hi all,<BR><BR>Is it considered bad practice to use application environment
variables (i.e. application:get_env/2,3) in workers, as opposed to only passing
config information via the start()/init() calls? I am finding it tedious as I
add more configuration data to the sys.config file, to get_env() the data in a
supervisor and then parcel it out to the workers. Also, it becomes a pain to
change the values at runtime, whereas if I put a function like this in an
affected worker<BR><BR>my_foo_val() -><BR>
application:get_env(my_app, my_foo_val, ?SOME_SANE_DEFAULT).<BR><BR>then runtime
changes can be made immediately using set_env(), and it becomes much easier to
add new config data, but I feel uneasy, almost as if I'm using global variables.
>From a load point of view, I only do this in places where the value is not used
at a high rate.<BR><BR>What is the preferred or recommended (or even most
common) practice?<BR><BR>Regards,<BR>Edwin Fine<BR>
<HR>
</DIV></BODY></HTML>