On Thu, 29 Jul 2010, Lyle wrote:
> On 29/07/2010 23:32, Jan Dubois wrote:
> > PerlScript and Perl for ISAPI are different things.
>
> I'm curious as to the mechanism from which the ASP script recognises
> PerlScript?
You must have a LANGUAGE=PerlScript attribute in your ASP script so that
ASP knows to load the PerlScript engine:
<%@ LANGUAGE = PerlScript%>
PerlScript itself is an "ActiveX Scripting Engine" that is registered as a COM
object in your registry.
> > However, both PerlScript and the Perl for ISAPI plugin (as well as PerlEx)
> > only work with 32-bit IIS, so you will need to enable 32-bit application
> > support for your App Pool.
>
> Hey that worked :D
Excellent! I was hoping it would.
> > Caveat: I'm only guessing here, I haven't actually tried running 32-bit Perl
> > on top of 64-bit IIS, so I don't know if it really works or not.
> >
>
> Is proper 64-bit support planned? It's all XML config files, so I would
> have thought having the ActivePerl install create the file mappings,
> etc, wouldn't be to hard... Or are you waiting for the 64-bit Perl on
> windows to mature more?
Well, the implementation of an ActiveX Scripting Engine is not just XML config
files, it is a whole bunch of C++ code that would need to be ported to 64-bit
mode. The actual registry of a COM object is not an issue; that code would
already work automatically.
It is not currently planned to do this porting effort unless a significant
number of people ask for it, for example via email to [email protected].
I don't know the current numbers, but someone *is* keeping count of these
requests. But if only 3 people ever ask for it, then it is unlikely that
we'll schedule 2 weeks of work to implement it (just making up some numbers
here).
Cheers,
-Jan
_______________________________________________
ActivePerl mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
