Re: [MacPerl] acgi vs cgi

[Richard Rathe <rrathe@dean.med.ufl.edu>]

On 11/9/97 Kostas Gewrgiou wrote:

> In a cgi the webserver locks up waiting for the cgi to complete (a really
>bad thing), in the case of acgi the webserver doesn't block and keeps
>accepting
>new connections its up to you agci how it will process them (sequentially or
>in a new thread).
>At least thats what i think they do, its been so long since i read the
>WebStars
>manuals and my memory fails me too often :(.

I've read the manual recently and it doesn't really help in the context of
MacPerl CGIs. It basically says what you state above, but it's unclear
whether this really MATTERS to MacPerl scripters!?! My take on it (someone
correct me if I'm wrong):

	ACGI is better in that the server is freed up to handle other
requests. This does NOT mean the ACGI will process more than one request at
a time, but the SERVER is able to serve other pages while the ACGI is
working. This may be pathological if the same ACGI is hit multiple times
over a short period. It is unclear to me what happens if the ACGI takes a
very long time to process (other server/client timeouts come in to play I
think). It is also unclear to me whether one needs to change MacPerl
scripts in any way to take advantage of ACGI. For example, the ACGIs I
tried DID NOT return any faster than CGI. I think this was because they had
to get to the first print statement before control was released. Since
printing the response HTML page is often the last thing my CGIs do, ACGI
really has no advantage as far as I can tell.

Corrections?

Thanks, RR

__________________________________________________________________________
  Richard Rathe, MD                       mailto:rrathe@dean.med.ufl.edu
  University of Florida                  http://www.med.ufl.edu/medinfo/  



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