Using MacPerl ACGI's with NetPresenz and/or Apple Web Sharing, I keep running into problems with stallouts. The scenario is that I call the ACGI from a link and it opens a file, extracts a portion of it, and returns that to the browser. That appears to work fine until I've run it 3-4 times in a row, then I eventually get a 502 bad gateway error even if it's just trying to retrieve the same chunk of text it already pulled in once before. This looks/feels very much like MacPerl is running out of gas, but I've got 10 megs allocated to it. The ACGI itself hangs and won't go away except via a force quit. Am I correct in understanding that the ACGI would not be likely to benefit >from an increase in memory since it is just passing AE on to MacPerl, or does it also deal with the output and assist in directing it to the web server? Does anyone have any other suggestions about how to contend with this kind of thing? BTW, I've been fighting this off and on for several months and the last time I tested this stuff in MkLinux using Apache, I didn't encounter the problem. Is it more likely that the stalls are related to MacPerl itself or the limits of the Mac web servers (neither of which actually hang or anything, they just return the bad gateway error). Thanks. Richard Gordon Gordon Consulting & Design Voice: 770-565-8267 Fax: 770-971-6887 ==== Want to unsubscribe from this list? ==== Send mail with body "unsubscribe" to macperl-webcgi-request@macperl.org