Re: Re: AS Libraries for stay-open CGIs
Re: Re: AS Libraries for stay-open CGIs
- Subject: Re: Re: AS Libraries for stay-open CGIs
- From: email@hidden
- Date: Fri, 16 Feb 2001 16:14:52 EST
In a message dated 2/16/01 2:52:03 PM, Richard Hartman wrote:
<snip>
>
>1) You do not want "a single stay-open library of utility handlers
accessible
>
>to all the CGIs." This will choke under load because it would not be
>
>multithreaded, and my understanding is that it would use a FILO (same as
>
>LIFO, but the acronym order highlights the problem) system for responding to
>
>requests, leading to slowness or worse, timeouts.
>
>
Wow. This is a biggie I hadn't considered...
>
>
One thing I am unclear on. Does the single-threaded nature of script
>
objects apply to an entire "script object library".
>
>
That is, if I have two separate stay-open CGIs, (presumably) they can
>
be in "simultaneous" play, each by separate users (right?). If I then
>
combine the two into a *single* stay-open CGI script with two entry
>
points, does the single-threaded nature of AS *prevent* simultaneous
>
execution of the two handlers because they reside in a single
>
stay-open script? Since my handlers can take some time to complete
>
their tasks (some being finder-related file operations), simultaneous
>
execution is important here.
Exactly. Two handlers in the same script cannot execute simultaneously, but 2
scripts will run in parallel. Applescript is very good (too good sometimes)
in yielding CPU time to other processes.
Sadly, I am told this will not change in MacOS X.
I am told that Frontier can "host" Applescripts and make them multithreaded,
but I have not pursued this due to the investment involved (almost $900).
However, depending on your budget, it may be worthwhile to investigate.
Jeff Baumann
email@hidden
www.linkedresources.com
10 days 6 hours 41 minutes....
How is it going to end?