>>>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. > >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? > > -nat > > > >***** Want to unsubscribe from this list? >***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch 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 :(. -Kostas. ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch