Re: [MacPerl] acgi vs cgi

[Strider <Strider@clarityconnect.com>]

At 6:05 PM -0500 11/8/97, Nat Irons wrote:
>>>But I'm not sure how this relates to MacPerl, as MacPerl can only execute
>>>one at a time anyway, right?
>>
>>True, but it has provisions to handle more than one connection at once.
>>That's what an ACGI does- it doesn't do multiprocessing. =)
>
>Multiprocessing, to me, means use of multiple processors.

Sorry- multitasking was the word I was looking for. I was kinda busy at the
time. =)

>My confusion is the difference, in Macperl's case, between .cgi (which I
>understand queues incoming requests and executes them sequentially) and
>.acgi (which from your description appears to do the same).  Am I missing
>something, or does acgi simply not mean much to MacPerl circa 1997?

Now, Matthias may disagree with me here (he'd be right =) but here's the
difference the way I understand it:

CGIs hold messages in queues (like you said) and deal with each person one
at a time, in order.

ACGIs deal with more than one connection at once (like an FTP server does),
although it may not actually be doing multitasking. It slips commands in
between one another quickly and makes the semblance of multitasking, the
way the old MacOS did.

So, ACGIs are usually preferable, because they don't make people wait for
another connection to be finished, which is a pain if that other connection
takes a long time.

- Strider



***** Want to unsubscribe from this list?
***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch