I'm working on a column for Perl Monthly on CGI programming with MacPerl and am particularly interested in flagging places where different installations (different Web servers, different versions of the MacOS, different networking setups) affect behavior. Unfortunately, I only have a few possibilities I can test myself, so I rely on what I have read in this group to help extend that list. I recall a discussion in this group relating to the problems resulting from the 5 minute delay before a MacPerl CGI quits. Because the MacOS doesn't allow replacement of a running file, it was not possible to test a new version of the CGI until that 5 minutes ran out. I have confirmed this behavior using Apple File Sharing. I cannot confirm it using FTP transfer, but believe it would be the same. However, I may have found a workaround. If, using Apple File Sharing, you mount the remote Mac's volume on your Mac, and if you edit the CGI in place using MacPerl, you can save revisions to the CGI while it is still running, and on subsequent invocations, the new version is run. The one cosmetic consequence is that you now see two copies of the CGI under the Apple menu; the old version and the new. (I suppose this wastes RAM as well.) Comments? -David Steffen- David Steffen, Ph.D. President, Biomedical Computing, Inc. <http://www.biomedcomp.com/> Phone: (713) 610-9770 FAX: (713) 610-9769 E-mail: steffen@biomedcomp.com ==== Want to unsubscribe from this list? ==== Send mail with body "unsubscribe" to macperl-webcgi-request@macperl.org