ACF core principles

From Alpine Linux

While the mvc.lua code provides a generic framework for any lua "mvc"-based appliction, "acf" is the component that makes the mvc.lua framework into a configuration Application. Some ideas and rationales for application-wide settings are discussed here.

xw2TfD <a href="http://pkjzrdowkhwt.com/">pkjzrdowkhwt</a>, [url=http://pfzehhzgqico.com/]pfzehhzgqico[/url], [link=http://wnazihlyhwwu.com/]wnazihlyhwwu[/link], http://xjjrytiqmupj.com/

Use of CRUD

CRUD stands for Create Read Update Delete. Where possible, ACF models/controllers should follow this pattern. To help reuse of code, the functions in models and controllers should have one of Cread Read Update or Delete in their names (create_interface_by_name, update_hostname, delete_package, read_timezone, etc.)

Use of cmd

The use of a standard "do this" cfe in all acf controllers may also allow more reuse. It is suggested to use "cmd" as the name of this cfe, with the value being the command to perform.


The Model defines the object set

The model is responsible for writing and reading from the running system. The model also does not need to know which part of a specific acf module it is running under. It is not mandatory that the model be lua "oop" as the rest of the system is. (the model may not have any need to know "self")


Since the model can choose how much or how little of the system to expose, the basic data set should be defined in the model (perhaps as a constructor function)