[asterisk-bugs] [JIRA] (ASTERISK-29686) Module loading should be more reasonable

[Brian J. Murrell (JIRA)]

Brian J. Murrell created ASTERISK-29686:
-------------------------------------------

             Summary: Module loading should be more reasonable
                 Key: ASTERISK-29686
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29686
             Project: Asterisk
          Issue Type: Improvement
      Security Level: None
          Components: Core/Configuration
    Affects Versions: 18.7.1
            Reporter: Brian J. Murrell


Module loading seems to be an all-or-none proposition currently.

One can choose {{autoload=yes}} and every module under the sun is loaded, regardless of whether it's used or not.

Or one can choose {{autoload=no}} but then one is responsible for discovering every module that one's configuration requires *AND* those modules' dependencies, recursively to load them explicitly.

In today's times, those seem an unreasonable choice of two nasty policy implementations.

It's not uncommon in today's module models for such models to understand their own dependencies, in the least.

Asterisk should support at least understanding dependencies, and loading them, as well as a "load on first use" model.

Moreover what makes the {{autoload=no}} policy even more draconian is that there is no **Total Use** counter (or even an **Ever Used** flag) to at least help the administrator know which {{autoload=yes}} modules have been in use and would need to be explicitly loaded with {{autoload=no}}.



--
This message was sent by Atlassian JIRA
(v6.2#6252)