On Sat, 30 Sep 2000 16:39:04 -0400, Adam Turoff wrote:
>I repeat:
>
>> >All of the other features offered by Lincoln Stein's CGI.pm should remain,
>> >but should not be deeply integrated into Perl6.
> ^^^
>:-)
>
>The proposed 'use cgi;' pragma is concerned with gluing Perl into a cgi
On Sat, Sep 30, 2000 at 07:30:03PM +0200, Bart Lateur wrote:
> >All of the other features offered by Lincoln Stein's CGI.pm should remain,
> >but should not be deeply integrated into Perl6.
>
> Eek, no! I don't want no steenking p() functions etc. to generate HTML
> on the fly! That is one featur
On 25 Sep 2000 06:01:57 -, Perl6 RFC Librarian wrote:
>All of the other features offered by Lincoln Stein's CGI.pm should remain,
>but should not be deeply integrated into Perl6.
No cookie support, please. Cookies should remain in a module.
--
Bart.
On 25 Sep 2000 06:01:57 -, Perl6 RFC Librarian wrote:
>Perl6 should be *easier* to write CGI programs than Perl5.
>To make CGI programming easier, this option/pragma should:
...
>Parse the CGI context, returning CGI variables into %CGI
I like that one.
>Not take up gobs of memory
That too
On Tue, Sep 26, 2000 at 12:04:50AM -0400, Adam Turoff wrote:
> On Mon, Sep 25, 2000 at 07:50:28AM +0100, Richard Proctor wrote:
> > On Mon 25 Sep, Perl6 RFC Librarian wrote:
> > > Turn on tainting
> >
> > What would it do on a platform that does not support Tainting?
>
> Is this a real issue? I
On Tue, Sep 26, 2000 at 04:41:21AM -0400, Alan Gutierrez wrote:
> > > > > Robust input parsing: yes.
> > > >
> > > > > General purpose output formatting: no, [...]
> > > >
> > > > > Rudimentary HTTP header emission: probably.
>
> So this is the definition of first-class?
Have you read the RFC
On Tue, 26 Sep 2000, iain truskett wrote:
> * Adam Turoff ([EMAIL PROTECTED]) [26 Sep 2000 17:15]:
> > On Tue, Sep 26, 2000 at 05:02:02PM +1100, iain truskett wrote:
> > > Is there much point having a lightweight CGI module? If you say 'I want
> > > it to load quickly', I say 'get mod_perl'.
Agr
> > General purpose output formatting: no, nyet, nein, non, "over
> > my dead body".
> I'm guessing you mean "nyet" to "general purpose formatting *only*". :-)
>
> After sending that last email, I was sitting here drinking a beer, and
> it occured to me that tons of headers all the use same form
ires=> 'now',
);
$mail_headers->add(
-from => '[EMAIL PROTECTED]',
-to => '[EMAIL PROTECTED]',
-subject => 'Re: RFC 288 (v1) First-Class CGI Support',
);
if(fork())
{
my $email = new Ema
On Tue, Sep 26, 2000 at 05:02:02PM +1100, iain truskett wrote:
> Is there much point having a lightweight CGI module? If you say 'I want
> it to load quickly', I say 'get mod_perl'.
There's more to it than just loading quickly. It should load quickly
as in "load everything that's absolutely nece
> The http_header() is a straw man intended to demonstrate that there
> are issues with shoving all of the outgoing HTTP headers into a simple
> variable. Not insoluable problems, but problems.
Agreed.
> I do like the idea of stacking HTTP headers and queueing them up
> before the first print
* Adam Turoff ([EMAIL PROTECTED]) [26 Sep 2000 16:44]:
> On Mon, Sep 25, 2000 at 09:34:41PM -0700, Nathan Wiger wrote:
> > Adam Turoff wrote:
[...]
> > If it imports a function, then it's a module. Perhaps what we should
> > look at doing is providing a lightweight CGI module instead?
Is there m
On Mon, Sep 25, 2000 at 09:34:41PM -0700, Nathan Wiger wrote:
> Adam Turoff wrote:
> > I'm thinking that whether the request came from a GET or a POST,
> > the un(HTTP)-escaped values will be in %CGI, just as CGI::params()
> > does.
>
> Like this?
>
>$CGI{fullname} = 'Nathan Wiger';
>$CG
Adam Turoff wrote:
>
> I'm thinking that whether the request came from a GET or a POST,
> the un(HTTP)-escaped values will be in %CGI, just as CGI::params()
> does.
Like this?
$CGI{fullname} = 'Nathan Wiger';
$CGI{creditcard} = '1234-1234-1234-1234';
I'm 99% sure that's what you're sayin
On Sun, Sep 24, 2000 at 11:16:46PM -0700, Nathan Wiger wrote:
> > Perl is frequently used in CGI environments. It should be as easy to write
> > CGI programs with perl as it is to write commandline text filters.
>
> First off, good idea, I do like this. Critiques:
>
> > Parse the CGI context, r
On Mon, Sep 25, 2000 at 03:17:33AM -0400, Alan Gutierrez wrote:
> On 25 Sep 2000, Perl6 RFC Librarian wrote:
> > First-Class CGI Support
>
> First-class CGI to me means HTML::Embperl.
It means a hundred different things to a hundred different Perl
programmers. Especially those writing mod_perl
On Mon, Sep 25, 2000 at 11:43:53AM +0100, Hildo Biersma wrote:
> For output generation, it becomes worse.
Output generation is a separate problem space altogether. Related,
but separate.
Should embperl be turned on simply because I have a CGI program
returning text, images or HTTP redirects
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 (n
On Mon, Sep 25, 2000 at 07:50:28AM +0100, Richard Proctor wrote:
> On Mon 25 Sep, Perl6 RFC Librarian wrote:
> > Turn on tainting
>
> What would it do on a platform that does not support Tainting?
Is this a real issue? Is there a platform where tainting isn't
supported?
> > Parse the CGI conte
> "Uri" == Uri Guttman <[EMAIL PROTECTED]> writes:
Uri> on the geek cruise, lincoln told me he had almost completed a total
Uri> rewrite of CGI.pm. i have not heard anything about it since then. we
Uri> should find out what he has done and possibly integrate it into perl6.
CGI 3.01 is in the
On Sun, 24 Sep 2000, Nathan Wiger wrote:
> > Offer simple functions to set HTTP headers (e.g. content type, result codes)
> How about %HTTP, which is just flushed on the first line of output?
>use cgi;
>$HTTP{'Content-type'} = 'text/html';
>print "Hello!"; # flushes %HTTP first
On Mon 25 Sep, Perl6 RFC Librarian wrote:
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> First-Class CGI Support
>
> Maintainer: Adam Turoff <[EMAIL PROTECTED]>
>
> To make CGI programming easier, this option/pragma should:
>
> Turn on ta
> "PRL" == Perl6 RFC Librarian <[EMAIL PROTECTED]> writes:
PRL> All of the other features offered by Lincoln Stein's CGI.pm
PRL> should remain, but should not be deeply integrated into Perl6.
PRL> Write a very small cgi.pm module that does as little as possible,
PRL> probably based o
> =head1 TITLE
>
> First-Class CGI Support
> Perl6 should be *easier* to write CGI programs than Perl5. One way to
> accomplish this is to add a C<-cgi> option to Perl, so that all of the
> mechanical setup is done automatically. That setup could also be done
> through a C pragma.
>
> To ma
Perl6 RFC Librarian wrote:
>
> =head1 ABSTRACT
>
> Perl is frequently used in CGI environments. It should be as easy to write
> CGI programs with perl as it is to write commandline text filters.
>
> =head1 DESCRIPTION
>
> Tom Christiansen proposed this in his perl6storm message:
>
>
* Greg Boug ([EMAIL PROTECTED]) [25 Sep 2000 17:46]:
[...]
> > The RFC should just be a little more specific on what's being
> > included and not included. Are any of the functions like header(),
> > h2(), footer()? What about %ENV manipulation functions? What do
> > people think?
> I think that
On 25 Sep 2000, Perl6 RFC Librarian wrote:
> =head1 TITLE
>
> First-Class CGI Support
First-class CGI to me means HTML::Embperl. It include a templating
lanaguage for creating HTML/XML pages and support for session management
via cookies.
Are we talking about having cookes close to the core?
> > Parse the CGI context, returning CGI variables into %CGI
> Which variables are you talking about? Everything you need is already in
> %ENV, as I'm sure you're aware.
Yeah, but its encoded... %CGI in an unencoded form would be a nice
thing. :)
> If you're talking about splitting up the query
> Perl is frequently used in CGI environments. It should be as easy to write
> CGI programs with perl as it is to write commandline text filters.
First off, good idea, I do like this. Critiques:
> Parse the CGI context, returning CGI variables into %CGI
Which variables are you talking about? E
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
First-Class CGI Support
=head1 VERSION
Maintainer: Adam Turoff <[EMAIL PROTECTED]>
Date: 24 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 288
Version: 1
Status: Developing
=head1 ABSTRACT
P
30 matches
Mail list logo
