extended version information from Mapserver

[Brent Fraser]

Wow, lot's of good ideas!

I think the plain old text format would be ok for quick command line
confirmation of what versions/options are linked in, but I do like the XML
idea too.  Could be some possibilities for remote configuration checking:

Wouldn't it be great if I could browse to a troublesome URL then be able to
say to a perplexed implementer: " Yep,  your version of Mapserver/GDAL is
capable of reading ECW, and the GDAL_DATA environment variable is set on
your system,  but it still can't find the ecw_cs.dat file required to
correctly identify the ECW's coordinate system, so no ECW images will be
rendered."

Hmmm.   Or maybe we just need to have a template variable to spit the DEBUG
output into the HTML (or XML?)...

Brent

----- Original Message ----- 
From: "Daniel Morissette" <dmorissette at DMSOLUTIONS.CA>
To: <MAPSERVER-DEV at LISTS.UMN.EDU>
Sent: Thursday, February 23, 2006 9:52 AM
Subject: Re: [UMN_MAPSERVER-DEV] extended version information from Mapserver


> Kralidis,Tom [Burlington] wrote:
> > This would be ONLY available from command line, right?  I wouldn't want
> > people being able to pick this off from a URL.
> >
>
> I think someone (Frank?) suggested having a way to embed it in the
> returned HTML like the current version info can currently be returned
> using [version] in the template.
>
> In my case I was thinking about being able to fetch and parse the
> detailed version info in MapScript.
>
> Daniel
> -- 
> ------------------------------------------------------------
>   Daniel Morissette               dmorissette at dmsolutions.ca
>   DM Solutions Group              http://www.dmsolutions.ca/
> ------------------------------------------------------------