On Wed, Sep 27, 2000 at 11:33:13AM -0700, Nathan Wiger wrote: > Ziggy, are you interested in this idea enough (at all?) to stick a note > about the 'header' function into the RFC? Or should I RFC it separately? Adding headers() to the core language (or a similar pragma that is automagically invoked by cgi) would make more sense to me. I'd be in favor of a new RFC. Adding it into cgi sounds like we're on the road to spontaneously reinventing CGI.pm... It has uses in HTTP, CGI and SMTP contexts, probably others. Would be nice if there were some sort of interaction with 'open http $url' as well. Perhaps that would be what supplies %HTTP (or %HEADERS) for incoming headers and does trickery with print and @HEADERS... Z.
- RFC 288 (v2) First-Class CGI Support Perl6 RFC Librarian
- Re: RFC 288 (v2) First-Class CGI Support iain truskett
- Re: RFC 288 (v2) First-Class CGI Support Philip Newton
- Re: RFC 288 (v2) First-Class CGI Support Nathan Wiger
- Re: RFC 288 (v2) First-Class CGI Supp... Adam Turoff
- Re: RFC 288 (v2) First-Class CGI Support James Mastros
- Re: RFC 288 (v2) First-Class CGI Support Adam Turoff
- Re: RFC 288 (v2) First-Class CGI Support Dan Sugalski
- Re: RFC 288 (v2) First-Class CGI Support Nathan Wiger
- Re: RFC 288 (v2) First-Class CGI Support Dan Sugalski
- Re: RFC 288 (v2) First-Class CGI Support Nathan Wiger
- Re: RFC 288 (v2) First-Class CGI Support Robert Mathews
- Re: RFC 288 (v2) First-Class CGI Support H . Merijn Brand
- Re: RFC 288 (v2) First-Class CGI Support Adam Turoff
- Re: RFC 288 (v2) First-Class CGI Support Bart Lateur