On Mon, Sep 25, 2000 at 10:09:03AM -0500, [EMAIL PROTECTED] wrote: > > =head1 TITLE > > > > First-Class CGI Support > > [...] > > To make CGI programming easier, this option/pragma should: > > > Should the option/pragma also do "something" with regards to > files opened for writing? > > They (nearly?) always require locking in a CGI environment... > > That is, should this feature do anything with regards to file locking? My first instinct is to say no. There is nothing inherent about file locking and CGI. CGI is a dain-bread interface for running insecure^Wremote programs. If, however, there was some sort of 'use autolock' or 'use writelock' pragma, then I suppose it would be sensible turn that on with 'use cgi' or 'perl -cgi'. Make sense? Z.
- Re: RFC 288 (v1) First-Class... iain truskett
- Re: RFC 288 (v1) First-Class... Alan Gutierrez
- Re: RFC 288 (v1) First-Class... Adam Turoff
- Re: RFC 288 (v1) First-Class CGI Supp... Nathan Wiger
- RE: RFC 288 (v1) First-Class CGI... Greg Boug
- Re: RFC 288 (v1) First-Class CGI Support Alan Gutierrez
- Re: RFC 288 (v1) First-Class CGI Support Adam Turoff
- Re: RFC 288 (v1) First-Class CGI Support Hildo Biersma
- Re: RFC 288 (v1) First-Class CGI Support Adam Turoff
- Re: RFC 288 (v1) First-Class CGI Support tadmc
- Re: RFC 288 (v1) First-Class CGI Support Adam Turoff
- Re: RFC 288 (v1) First-Class CGI Support Uri Guttman
- Re: RFC 288 (v1) First-Class CGI Support Randal L. Schwartz
- Re: RFC 288 (v1) First-Class CGI Support Richard Proctor
- Re: RFC 288 (v1) First-Class CGI Support Adam Turoff
- Re: RFC 288 (v1) First-Class CGI Support Jonathan Scott Duff
- Re: RFC 288 (v1) First-Class CGI Support Bart Lateur
- Re: RFC 288 (v1) First-Class CGI Support Adam Turoff
- Re: RFC 288 (v1) First-Class CGI Support Bart Lateur
- Re: RFC 288 (v1) First-Class CGI Support Bart Lateur