httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff White" <jlw...@earthlink.net>
Subject Re: cvs commit: httpd-2.0/modules/arch/win32 mod_win32.c
Date Tue, 25 Mar 2003 19:58:59 GMT

From: "William A. Rowe, Jr."

>>
>> Doesn't the Apache on Windows web server have
>> available a built-in Windows Scripting Engine and two
>> built-in scripting languages, that do not use the # as
>> a scripting comment marker?

> No; Windows has a command-line Windows Scripting Host
> (cscript, as opposed to the window-based wscript).

<quote>

The Windows Scripting Engine serves as the component
within Windows that interprets and executes script code
written in scripting languages such as JScript or VBScript.

</quote>

This Windows Scripting Engine component is used by
many types of "hosts":

Windows Script Host - (WSH 5.6) has two parts.
   Cscript.exe  - CUI - command line  (like Perl.exe)
                        Accesses COM and file system, StdIn,
                        StdErr and StdOut for usage as say admin
                        config type scripts or for accessing LDAP
                        or ADSI or WMI or databases or Regex and
                        etc. (lots more) on the desktop or server to
                        server.
                        Could run in Apache on Windows web server.

  Wscript.exe - GUI - output in window boxes on the screen
                       much like those in the MsgBox. Same usage
                       as Cscript.exe above but with different output.
                       Best for desktop usage for admin type "config"
                       usage same as Cscript.exe above but with the
                       different output way (MsgBox style).
                       Should not be used in Apache on Windows.

Http Applications - HTA - Html files that run on the desktop
                        but not via the browser.  Uses a separate DLL.
                        Accesses some COM and file system like WSH
                        but is not the Windows Script Host.
                        Desktop and server or to server.
                        Could run on as Intranet usage with Apache on
                        Windows.  Not for the Internet.

Internet Explorer - Browser usage.
                        Internet - limits on Com and file system.
                        Desktop - used for displays of list boxes,
                        radio and combo boxes with WSH scripts.

OS - Used in the Windows OS.
                        No need here to explain DLLs usage.

ASP - Used in IIS.
                      (Sort of, but close enough for here without
                      explaining all the DLLs used by everything.)

Programs -  Windows and third party programs.
                     Calls the Com access to the engine and
                     the scripting language usage is available.

So the Windows Script Host is one of many ways
that  "the Apache on Windows web server have
available a built-in Windows Scripting Engine and two
built-in scripting languages, that do not use the # as
a scripting comment marker".

There are a lot of add-in (downloadable) languages for
usage with the Windows Scripting Engine.  But there
are only two built-in languages, VBScript and JScript.

> As André indicated, this is most trivially enabled using the
> Registry-based ScriptInterpreterSource directives.  It is actually
> recommended that you use ScriptInterpreterSource registry-strict
> which will invoke the ExecCGI verb, instead of using the Open
> verb.

Since it "is most trivially enabled using the Registry-based
ScriptInterpreterSource directives" then why is this not the
default (unneeded to turn on) for _all_ Apache on Windows?

This ScriptInterpreterSource default would allow usage of the
built-in Windows Scripting Engine as well as any other Windows
OS "known" programs, such as Perl.  There would be no need
for _any_  scripting comment marker checking routine with the
Apache on Windows web server.

But if any scripting comment marker checking routine (of the
"shebang" type), is performed, on Apache on Windows, without
first having the ScriptInterpreterSource as the default, then this
"component within Windows" that is available to every Apache
on Windows web server, the built-in Windows Scripting Engine
and it's built-in default languages, should be included into this
scripting comment marker checking routine first, if not at least,
somewhere in the #! checking routine in Apache on Windows.

But if it is "compat ways" one seeks, then have the Unix type
Apache versions, only check for ' (a single quote) and then
the Unix type versions of Apache, can run two files also!  :)

> This patch is a no-op relative to VB/J Scripts.

But one added a BOM change (so changes are allowed)
and yet left the #!, that is not used with Windows Scripting
Engine's built-in default languages, available in all Apache
on Windows web servers.

There are many scripting languages, so if any scripting comment
marker checking routine is needed, on Apache on Windows,
then an option for scripting languages is needed too.

A lot is happening with the Windows Scripting Engine. And most
people only use it "properly" with the other Windows "products".
So for them, there is no need for what sounds like "odd and weird"
usage. But these "strange usage ways" work with the Windows
Scripting Engine and may only be needed with non standard
Windows "products".  :)

Just wait 'til one is using some of the .NET Framework 40+
languages in the Apache on Windows web server, for some
unusual Windows usage ways!  ;)

Jeff





Mime
View raw message