Hi Sergey:
Granted this is your software, and you are free to take it down any path you
desire, but I'd like to make a case for leaving in the configuration file (but
I applaud you for adding command-line for all operating systems, I would just
like you to support BOTH configuration file & command-line)
Reasons include:
1. Security - All one has to do is enter something like ps -ef, and anybody can
see the command-line options, which unnecessarily reveals aspects of how the
instance is configured.
2. Implementation constraints - Operating systems vary on the maximum byte
length of command-line parameters.
3. Field delimiters - What if you need to embed single and/or double-quotes,
white-space, non-printable characters, or unix-style expressions in any of the
fields? The command-line interpreter is different between Windows/UNIX, so
you can potentially get different results from same command-line syntax. This
also means everybody has to add more documentation and OS-specific
modifications. Furthermore, there can and will be differences depending on
what shell the user is running.
I for one, will have to modify code to tell program the name of the
configuration file, because of reasons I mentioned above. I expect others will
have to do the same.
David
________________________________
From: [EMAIL PROTECTED] on behalf of Sergey Lyubka
Sent: Tue 2/12/2008 4:16 AM
To: Fred
Cc: shttpd-general
Subject: Re: [shttpd-general] [1.38 Win] How to encrypt .htpasswd?
No, 1.39 does not have conf file anymore - only command line args. For
the not experienced users, it would be very easy: copy shttpd.exe to
the directory you want to serve and double-click it, that's all.
For the more advanced it is possible to make a shortcut or .bat file,
and specify command line arguments.
On 12/02/2008, Fred <[EMAIL PROTECTED]> wrote:
> At 09:17 12/02/2008 +0000, Sergey Lyubka wrote:
> >That means when you start it, it'll open console window.
>
> Definitely not a good thing :-/ I'm sending SHTTPD to someone who doesn't
> know the first thing about computers, so that it should just run after I
> copy the .EXE and the .CONF file in a target directory. The less hassle,
> the better.
>
> As for adding SHTTPD as a service, it's a nice option, but how will users
> interact with it? For instance, what if I need to launch SHTTPD with
> different options? By editing its .CONF file?
>
> Thanks.
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
shttpd-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shttpd-general
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
shttpd-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shttpd-general
