Christopher Barker wrote:
>has wrote:
>>CGI's always going to be expensive as it starts a new process for each
>>request. And yeah, if it's a GUI process then the overheads will bite even
>>more.
>
>Yes, but it sounded like the OP was getting over a second start-up time. This
>is very long, so
Ryan Wilcox wrote:
>I have a bunch of CGIs that make use of pythonw (+cgiwrap) to allow me
>to send AppleEvents (via appscript) to applications on the web server
>machine.
CGI's always going to be expensive as it starts a new process for each request.
And yeah, if it's a GUI process then the o
On Wed, Dec 07, 2005 at 06:18:49AM +, Ryan Wilcox wrote:
> Hello all,
>
> I have a bunch of CGIs that make use of pythonw (+cgiwrap) to allow me
> to send AppleEvents (via appscript) to applications on the web server
> machine.
>
> Everytime I hit one of these CGIs, pythonw launches a Pyt
Hello all,
I have a bunch of CGIs that make use of pythonw (+cgiwrap) to allow me
to send AppleEvents (via appscript) to applications on the web server
machine.
Everytime I hit one of these CGIs, pythonw launches a Python
application (which makes sense). While this machine is under heavy-is
