The same XML Dialplan and User Directory (and actually all of the FreeSWITCH configuration) we saw in previous chapters can be served dynamically to FreeSWITCH, changing in real time, instead of being read from the filesystem.
Also, this is not an all or nothing choice: you can serve dynamically just the User Directory, or the dialplan, or the module configurations. And you can have fall-backs on filesystem that are read when the dynamic configuration is not covering that specific looked for item (as in "404 File not found").
You can serve that XML information via a web server to mod_xml_curl, or you can use scripts in supported languages (Lua, Perl, and so on). Scripts can do whatever to build the XML snippet to be returned to FreeSWITCH (query a database, use a template, and so on).
Each time FreeSWITCH needs to know something (a user configuration, or a dialplan extension) it will use the script (or mod_xml_curl) to retrieve...