David, You said: >the .acgi suffix. I say unfortunately in that this ALSO signals to >QPQ that your CGI can handle a second request while the first is >still processing, which is very much not true and results in anything >from a dropped request to a crashed server. For a public server I I've heard this before, and I recall something on the MacPerl site mentioning it too. However, I haven't seen all that much about it and I was wondering if there was some more info somewhere. Maybe a work-around with a master program directing others when they're free? Or a "status" command that would return whether or not another program is running? Or other ways that I haven't thought of? =) Unix Perl, of course, doesn't have this problem. Is the problem solely because of the Mac's limited threading? Or is this something that could be fixed in a future version of MacPerl? Thanks! --Ian -- ----------------------------------------------------------- Ian Cabell - ian@yak.net - There Is More Than One Right Way PGP Key: C5A5 560D 2E28 FF1F BA6D C2C7 870C 8ED5 8AF0 79C5 ==== Want to unsubscribe from this list? ==== Send mail with body "unsubscribe" to macperl-webcgi-request@macperl.org