W3C home > Mailing lists > Public > xproc-dev@w3.org > November 2008

Re: Configuration options

From: Florent Georges <fgeorges@fgeorges.org>
Date: Tue, 11 Nov 2008 15:04:05 +0100
Message-ID: <ebaca5bf0811110604g322badb7q98bf9ef90e18430a@mail.gmail.com>
To: "Norman Walsh" <ndw@nwalsh.com>
Cc: "XProc Dev" <xproc-dev@w3.org>

2008/11/11 Norman Walsh wrote:

> What's the right answer here? A Java .properties file on the class
> path? A new command line option to point to an (XML) configuration
> file? A ".file" in the current/home directory?

  Between Java properties and an XML file, I think we'll all agree :-)
 We are used to think hierarchically with XML, and I think Java
properties are frustrating in that regard (and usually soon become a
mess.)

  For option vs. a file in home directory, I think the typical Unix
shell approach has proven successful: look at a Java property pointing
to such a config file (set from the Java calling program or from the
command line) then look in the current dir for a file with a specific
name, then look in the home dir and eventually look in the site-wide
config dir (/etc or whatever.)

  This way, admins can set options at the site level (connections,
proxy...) then the user at her level (in her home) then at one
application or project level.

  Hope that helps,

-- 
Florent Georges
http://www.fgeorges.org/
Received on Tuesday, 11 November 2008 14:04:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 November 2008 14:04:42 GMT