Alan Gutierrez wrote: > > This header functionality is application specific and does not belong in > the core any more than the socket stuff which seems to be on its way > out. I don't see why this has be implemented in the core in C. > > Once again, if core means core modules, and as a part of cgi.pm or > headers.pm or some such I am not concerned. And a switch for tainting > and inclusion of this module sounds peachy. No core. Yes, I believe that is the idea, at least currently. CGI.pm is also massive because it also includes a whole bunch of h2() and like methods that we wouldn't need here. The idea is just to cover basic stuff that modules like CGI.pm could potentially build on. -Nate
- Re: RFC 288 (v2) First-Class CGI ... Alan Gutierrez
- Re: RFC 288 (v2) First-Class CGI ... iain truskett
- Re: RFC 288 (v2) First-Class CGI Support Philip Newton
- Re: RFC 288 (v2) First-Class CGI Supp... iain truskett
- Re: RFC 288 (v2) First-Class CGI ... Philip Newton
- Re: RFC 288 (v2) First-Class CGI Support Nathan Wiger
- Re: RFC 288 (v2) First-Class CGI Support Adam Turoff
- Re: RFC 288 (v2) First-Class CGI Support Nathan Wiger
- Re: RFC 288 (v2) First-Class CGI Support Hildo Biersma
- Re: RFC 288 (v2) First-Class CGI Support Alan Gutierrez
- Re: RFC 288 (v2) First-Class CGI Support Nathan Wiger
- Re: RFC 288 (v2) First-Class CGI Support iain truskett
- Re: RFC 288 (v2) First-Class CGI Support Alan Gutierrez
- 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 Supp... James Mastros
- Re: RFC 288 (v2) First-Class CGI ... Dan Sugalski
- Re: RFC 288 (v2) First-Class CGI ... Nathan Wiger