Here are the pros and cons of each of the possible formats:
xml: the original format. XML was chosen so it would be possible to
tinker with source capabilitites documents, although this is not an
actual usecase (yet?) :
+ parser already written, format is in use
- verbose syntax (need to write closing tags, quote strings, ..)
+/- rather well structured, except when defining arrays (e.g. extents
or resolutions)
json: http://code.google.com/p/mod-geocache/source/browse/trunk/geocache.json
+ parser already written
- users will need to convert from xml
+ well structured
+/- less verbose than xml, but the need for quoted keys and [] {}
separators makes the final result not very legible
+/- json spec does not allow comments, although the included
mod-geocache parser has been patched to support them.
yaml: http://code.google.com/p/mod-geocache/source/browse/trunk/static/geocache.yaml
+ in my opinion the most legible and pleasant format for hand-editing
+ well structured (arrays, comments, lists, etc..)
- users will need to convert from xml
- added dependency on libyaml (although we could imagine including it
in the source distribution)
- parser not written, and rather complex to implement
other: flex/bison custom format
+ can be made legible, and close to the already known mapserver syntax
+ no external dependency
- parser not written
- users will need to convert from xml
- difficult to programmatically generate config files
regards,
Thomas
Steve
regards,
Thomas
--
You received this message because you are subscribed to the Google Groups "mod-geocache" group.
To post to this group, send email to mod-ge...@googlegroups.com.
To unsubscribe from this group, send email to mod-geocache...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mod-geocache?hl=en.
Personally, I've found the XML quite reasonable to edit.
My 1.99 c:
xml: +1
yml: 0
json: 0
custom parser: -1
Peter
R3 GIS
http://www.r3-gis.com
-jeff
regards,
thomas
I'm happy with XML, although as a human, I would prefer YAML.
But my first concern is the speed. If I have thousands of sources and
tilesets and need to restart Apache often, one more second for loading
the config matters to me.
+1 xml
0 json
+1 yaml
0 custom
Jean-François Gigand - Geonef
Paris, France - http://geonef.fr/
2011/8/16 thomas bonfort <thomas....@gmail.com>: