/************************************************************************* * * $RCSfile: bootstrap.h,v $ * * $Revision: 1.3 $ * * last change: $Author: jbu $ $Date: 2001-10-24 10:51:08 $ * * The Contents of this file are made available subject to the terms of * either of the following licenses * * - GNU Lesser General Public License Version 2.1 * - Sun Industry Standards Source License Version 1.1 * * Sun Microsystems Inc., October, 2000 * * GNU Lesser General Public License Version 2.1 * ============================================= * Copyright 2000 by Sun Microsystems, Inc. * 901 San Antonio Road, Palo Alto, CA 94303, USA * * This library is free software; you can redistribute it and/or * modify it under the terms of the GNU Lesser General Public * License version 2.1, as published by the Free Software Foundation. * * This library is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU * Lesser General Public License for more details. * * You should have received a copy of the GNU Lesser General Public * License along with this library; if not, write to the Free Software * Foundation, Inc., 59 Temple Place, Suite 330, Boston, * MA 02111-1307 USA * * * Sun Industry Standards Source License Version 1.1 * ================================================= * The contents of this file are subject to the Sun Industry Standards * Source License Version 1.1 (the "License"); You may not use this file * except in compliance with the License. You may obtain a copy of the * License at http://www.openoffice.org/license.html. * * Software provided under this License is provided on an "AS IS" basis, * WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, * WITHOUT LIMITATION, WARRANTIES THAT THE SOFTWARE IS FREE OF DEFECTS, * MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE, OR NON-INFRINGING. * See the License for the specific provisions governing your rights and * obligations concerning the Software. * * The Initial Developer of the Original Code is: Sun Microsystems, Inc. * * Copyright: 2000 by Sun Microsystems, Inc. * * All Rights Reserved. * * Contributor(s): _______________________________________ * * ************************************************************************/ #ifndef _RTL_BOOTSTRAP_H_ #define _RTL_BOOTSTRAP_H_ #include #ifdef __cplusplus extern "C" { #endif /** @HTML @file The described concept provides a platform independent way to access minimum bootstrap settings for every application by excplitly or implicitly passing the values to the application.

4-LEVEL STRATEGY FOR RETRIEVAL OF BOOTSTRAP VALUES :

The 1st level is tried first. On failure, the next level is tried. Every query starts at the first level again, so that one setting may be taken from the 3rd and one from the 1st level.

1st level: command line arguments. A "-env:SETTINGNAME=value" is given on command line. This allows to give an application a certain setting, even if an ini-file exists (espicially useful for e.g. daemons that want to start an executable with dynamical changing settings).

2nd level: ini-files. Every application looks for an ini-file. The filename defaults to /absoulte/path/to/executable[rc|.ini] (without .bin or .exe suffix). The ini-filename can be set by the special command line parameter '-env:INIFILENAME=/absolute/path/to/inifile' at runtime or it may be set at compiletime by an API-call.

3rd level: environment variables. The application tries to get the setting from the environment.

4th level: default. An application can have some default settings decided at compile time, which allow the application to run even with no deployment settings.

If neither of the 4 levels leads to an successful retrieval of the value (no default possible), the application may fail to start.

NAMING CONVENTIONS

Naming conventions for names of bootstrap values : Names may only include characters, that are allowed charcters for environment variables. This excludes '.', ' ', ';', ':' and any non-ascii character. Names are case insensitive.

The ini-file is only allowed to have one section, which must be named '[Bootstrap]'. The section may be omitted. The section name does not appear in the name of the corresponding environment variable or commandline arg. Values maybe arbitrary unicode strings, they must be encoded in UTF8.

Example:

in an ini-file: [Sectionname] Name=value

as commandline arg: -env:Name=value

as environment setenv Name value set Name=value

SPECIAL VARIABLES: