[Mapbender-dev] hardwired version number
Christoph Baudson (WhereGroup)
christoph.baudson at wheregroup.com
Tue Jan 8 05:41:13 EST 2008
On Monday we discussed this at the IRC meeting, citing the protocol
--
e) Where to put the version number of Mapbender?
Kicked off by Marko's idea back in September:
http://lists.osgeo.org/pipermail/mapbender_dev/2007-September/000685.html
The idea is to have the version number of Mapbender hardwired, so that
Mapbender "knows" what version it has. There were various ideas
- in mapbender.conf
- a new constants.php file
- a new version.txt file
We still need to work out which solution will be best.
Marko proposed to also store the version number in the database in order
to check if the database is compatible to the software, which was
believed to be a sensible idea.
--
My idea is to have a new PHP file that contains system constants, maybe
called system.php. This could be located in "php". The following
arguments led me to my suggestions:
- a PHP file indicates it is a machine readable file, and not a user
readable file
- declaring it as a constant (and not storing it in the conf folder)
will indicate that it's not to be changed
- a javascript variable could easily be derived from that constant
- the php file is extendable for other possible system wide constants
The reason I would advise against a conf file is
- that the version number is not configurable
The reason I would advise against a txt file is
- a txt file would suggest that it is regarded human readable, and not
machine readable.
- including a txt file in a php file is not good style
Please share your thoughts.
--
_______________________________________
W h e r e G r o u p GmbH & Co. KG
Siemensstraße 8
53121 Bonn
Germany
Christoph Baudson
Anwendungsentwickler
Fon: +49 (0)228 / 90 90 38 - 25
Fax: +49 (0)228 / 90 90 38 - 11
christoph.baudson at wheregroup.com
www.wheregroup.com
Amtsgericht Bonn, HRA 6788
_______________________________________
Komplementärin:
WhereGroup Verwaltungs GmbH
vertreten durch:
Arnulf Christl, Olaf Knopp, Peter Stamm
_______________________________________
More information about the Mapbender_dev
mailing list