Hi, On Sat, Sep 21, 2013 at 7:50 AM, Zeno Tajoli <[email protected]> wrote:
> I have to define a configuration file for Koha. > Which perl module do we want to prefer for config files ? > YAML (like system prefences) or XML::Simple (like koha-conf.xml) ? > Well, the choice seems to be YAML vs. XML as file formats -- there are much better XML parsers than XML::Simple available. JSON would be an option as well, though not the most friendly. Ditto for Perl-as-config-file-format. One downside of YAML is that it can be a bit too sensitive to mistakes in whitespace. The nit about XML processors aside, how complicated is the structure of the configuration data you need to express? And how frequently would a human need to look at it? If the configuration you need to express boils down to a hash map, I suggestion a simple key-value format such as a properties file or even an INI file. Also, is there anything preventing the configuration from living in the database? Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: [email protected] direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
_______________________________________________ Koha-devel mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
