At 11:00 AM -0600 3/18/00, David Steffen wrote: >Bruce: > >Thank you so much for responding - this is exactly the feedback I >desperately need! [snip] > >In reply to your specific question: > [snip] >So, you might have a bazillion CGIs all happily running at the same >time and all is well. You don't get into trouble unless you get >overlapping hits to MacPerl. If your Perl scripts run very quickly, >this is unlikely to happen. If you have one or more scripts that >take a while to complete and/or your website starts to get a lot of >traffic, then you have trouble. > OK. This clarifies what you meant. My use of MacPerl/CGI is usually _not_ for public web sites, so overlapping calls to MacPerl are rare. I'll watch more closely next time I do some process that takes a long time. I do get crashes occasionally with MaPerl/CGI, but I hadn't noticed a clear pattern. And of course I agree with your suggestion for using a single CGI made versatile by having many subroutines or calls to other modules. This works well with my usual approach to developing CGIs, which I develop on Mac but mostly end up delivering to *nix or NT. When I first set up a site for a client (or provide them the setup package, if that's their security condition), the first thing installed is a package of standard scripts, organized as subroutines in a single script/module. These do things like read out info about the OS, web server, Perl version, CGI.pm version, etc., and test user input and file access. If these scripts work, then custom code can be built on a familiar base. In this approach, sometimes it's easiest to just drop the custom code into the standard 'package' (script/module) as added subroutines. If so, then consistently with your suggestion, what I develop on Mac as a single multi-function MacPerl script can go directly to its new home/platform with no change. Anyway, KUTGW on your article. I'll read over your latest draft again in a few days. -- - Bruce __Bruce_Van_Allen___bva@cruzio.com__Santa_Cruz_CA__ ==== Want to unsubscribe from this list? ==== Send mail with body "unsubscribe" to macperl-webcgi-request@macperl.org