Currently we are using globals_get and globals_set to read and potentially set settings that pertain to the db or ORM or other areas. Those settings can be loaded using an ini file available to the webserver or CLI process.
We need a better way of dealing with those, especially considering the phalcon project which is written in PHP and does not have the option to store custom settings. The ini settings in cphalcon come from internal operations, where phalcon only has the option of ini_set which will not allow new settings to be added.
Additionally, globals_set sets the setting globally and not per request. As such if process A uses a globals_set, it will affect process B running on the same web server.
We need to remove this leak and allow only getting and setting within the same request. This most likely will lead to the deprecation of globals_set.
Currently we are using
globals_getandglobals_setto read and potentially set settings that pertain to the db or ORM or other areas. Those settings can be loaded using an ini file available to the webserver or CLI process.We need a better way of dealing with those, especially considering the phalcon project which is written in PHP and does not have the option to store custom settings. The ini settings in cphalcon come from internal operations, where phalcon only has the option of
ini_setwhich will not allow new settings to be added.Additionally,
globals_setsets the setting globally and not per request. As such if process A uses aglobals_set, it will affect process B running on the same web server.We need to remove this leak and allow only getting and setting within the same request. This most likely will lead to the deprecation of
globals_set.