<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=Windows-1252">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.0.6618.4">
<TITLE>RE: [mapguide-psc] MapGuide's 1st RFC!</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>I have changed the RFC to reflect that both "/" and "-" will work, but that the commandline help only shows the "-" options. Also, "interactive" will still be supported, but "run" is the new short version. :)<BR>
<BR>
Bruce<BR>
<BR>
-----Original Message-----<BR>
From: Tom Fukushima<BR>
Sent: Tue 10/31/2006 8:22 PM<BR>
To: psc@mapguide.osgeo.org; dev@mapguide.osgeo.org<BR>
Cc: <BR>
Subject: RE: [mapguide-psc] MapGuide's 1st RFC!<BR>
<BR>
Yes, I would like to see both formats ("/" and "-") supported as well.<BR>
<BR>
But when the user gets the command line help by typing "mgserver -?" or<BR>
"mgserver --help" (note the double dash), I propose that we only show<BR>
the "-" versions of the options. Of course, this is a bit confusing to<BR>
those users who want to figure out what /interactive means; Bruce, why<BR>
are we changing "interactive" to "run"? Or will "mgserver -interactive"<BR>
also work?<BR>
<BR>
<BR>
So typing "mgserver --help" outputs:<BR>
<BR>
The following is a list of supported command line options:<BR>
<BR>
-? or --help<BR>
Displays this information.<BR>
<BR>
-install <Name><BR>
Installs the server as a service. Automatically starts the<BR>
service.<BR>
<BR>
Default service display name installed:<BR>
"MapGuide Server"<BR>
<BR>
You can use a different display name for the service if you<BR>
specify an<BR>
optional "Name".<BR>
<BR>
-run<BR>
Runs the server interactively as an application instead of a<BR>
service.<BR>
<BR>
-start<BR>
Starts the server service. Note: The service must be installed.<BR>
<BR>
-stop<BR>
Stops the server service. Note: The service must be installed.<BR>
<BR>
-testfdo <Filename><BR>
Runs the FDO unit tests.<BR>
<BR>
Default output of the FDO unit tests will be the console unless<BR>
you<BR>
specify an optional "Filename". The output to the "Filename" will<BR>
be<BR>
in XML.<BR>
<BR>
-test <Test> /o <Filename><BR>
Runs the server unit tests.<BR>
<BR>
By default all of the unit tests will be run unless you specify an<BR>
optional "Test" to run. If you specify "List" as the test to run<BR>
you<BR>
will get a list of the available unit tests.<BR>
<BR>
Default output of the unit tests will be the console unless you<BR>
specify<BR>
an optional "Filename". The output to the "Filename" will be in<BR>
XML.<BR>
<BR>
-uninstall<BR>
Uninstalls an installed server service. Automatically stops the<BR>
service<BR>
before uninstalling.<BR>
<BR>
<BR>
Note: Only 1 command line option can be used at a time.<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Bruce Dechant<BR>
Sent: Tuesday, October 31, 2006 2:49 PM<BR>
To: psc@mapguide.osgeo.org<BR>
Subject: RE: [mapguide-psc] MapGuide's 1st RFC!<BR>
<BR>
I will be easy enough to support both. I'll update the RFC to reflect<BR>
this.<BR>
<BR>
Bruce<BR>
<BR>
-----Original Message-----<BR>
From: Andy Morsell [<A HREF="mailto:amorsell@spatialgis.com">mailto:amorsell@spatialgis.com</A>]<BR>
Sent: October 31, 2006 12:42 PM<BR>
To: psc@mapguide.osgeo.org<BR>
Subject: RE: [mapguide-psc] MapGuide's 1st RFC!<BR>
<BR>
I agree, it's probably not a big issue. It depends on how much work it<BR>
would be on Bruce's end to support backwards compatibility. If it would<BR>
be relatively easy, then may as well do it. If it would require a large<BR>
effort, then the current console response to an incorrect parameter<BR>
should be sufficient for users to figure it out on their own.<BR>
<BR>
<BR>
Andy<BR>
<BR>
-----Original Message-----<BR>
From: Paul Spencer [<A HREF="mailto:pspencer@dmsolutions.ca">mailto:pspencer@dmsolutions.ca</A>]<BR>
Sent: Tuesday, October 31, 2006 11:29 AM<BR>
To: psc@mapguide.osgeo.org<BR>
Subject: Re: [mapguide-psc] MapGuide's 1st RFC!<BR>
<BR>
I am normally a big fan of backwards compatibility too, but I really<BR>
don't see this as a big issue. Perhaps if the tool just spits out an<BR>
appropriate message if called with incorrect parameters?<BR>
<BR>
Then again, windows users are most likely used to the / style of adding<BR>
parameters so perhaps that makes it worthwhile supporting both?<BR>
<BR>
Paul<BR>
<BR>
On 31-Oct-06, at 2:08 PM, Andy Morsell wrote:<BR>
<BR>
> I agree with Frank in that keeping it backwards compatible with the<BR>
> older command line parameters while in the future only documenting the<BR>
<BR>
> new ones would be the best. There are many references, mostly in<BR>
> archived messages in the mapguide-users mailing list, to the current<BR>
> parameter syntax that new users are bound to run across (and try to<BR>
> use) when doing research.<BR>
><BR>
> Regarding the RFC format, that seems to work very well.<BR>
><BR>
> Andy<BR>
><BR>
> From: Bruce Dechant [<A HREF="mailto:bruce.dechant@autodesk.com">mailto:bruce.dechant@autodesk.com</A>]<BR>
> Sent: Tuesday, October 31, 2006 10:20 AM<BR>
> To: psc@mapguide.osgeo.org<BR>
> Subject: [mapguide-psc] MapGuide's 1st RFC!<BR>
><BR>
> Hi All,<BR>
><BR>
><BR>
><BR>
> I wrote up a simple MapGuide RFC to give our process a trial run.<BR>
><BR>
><BR>
><BR>
> <A HREF="http://wiki.osgeo.org/index.php/MG_RFC_1_-">http://wiki.osgeo.org/index.php/MG_RFC_1_-</A><BR>
> _Commandline_parameter_changes<BR>
><BR>
><BR>
><BR>
> Please have a look and post any feedback.<BR>
><BR>
><BR>
><BR>
> Thanks,<BR>
><BR>
> Bruce<BR>
><BR>
><BR>
><BR>
><BR>
<BR>
+-----------------------------------------------------------------+<BR>
|Paul Spencer pspencer@dmsolutions.ca |<BR>
+-----------------------------------------------------------------+<BR>
|Chief Technology Officer |<BR>
|DM Solutions Group Inc <A HREF="http://www.dmsolutions.ca/">http://www.dmsolutions.ca/</A> |<BR>
+-----------------------------------------------------------------+<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>