Eric Smith wrote:
>
> Hi
>
> I mailed recently on this subject but received no response :( so lets try
> again *shrugs*.
>
> I develop in perl for win32 end-users. We have chosen to deploy the perl
> as cgi scripts so user has a browser interface on the local machine
> (obviously this is scalable to internet and that is the main motivation
> for this approach).
>
> A currently unresolved drawback is /performance/ due to the follwing
> factors IMO:
> 1. compiling with perlapp to exe -major issue
If you're deploying the scripts via CGI, why are you converting them to
EXE? The major win of perlapp, perl2exe, et al is deployment (the
ability to distribute perl scripts without the need to install perl on
each workstation). By placing the scripts on a central server (the
wiser course of action, IMO), this becomes a non-issue. Just install
Perl on the Xitami server and be done with it.
HTH,
Ian
--
99 little bugs in the code, 99 bugs in the code.
Fix one bug, compile again, 100 little bugs in the code.
100 little bugs in the code, 100 bugs in the code.
Fix one bug, compile again, 101 little bugs in the code...
---
You are currently subscribed to perl-win32-users as: [archive@jab.org]
To unsubscribe, forward this message to
[EMAIL PROTECTED]
For non-automated Mailing List support, send email to
[EMAIL PROTECTED]
