On 27 Sep 2000, at 23:48, iain truskett wrote: > So surely you'd want %HTTP (the input headers) to also be an array > rather than a hash, since they'd be required in order as well? I don't care, because I don't work with this much. And I don't know whether I'd need to bear in mind the protocol which requires the order; I'd probably want to access them randomly. But that I send out has to follow the protocol. In other words, the input has an order (the order in which the user- agent sent the headers), but I'm not necessarily interested in it (frequent CGI programmers may have different needs); the output also has an order, and *someone* has to provide for that order, and I believe it is not good for Perl to do so (for the reasons given before). Cheers, Philip
- 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
- Re: RFC 288 (v2) First-Class CGI Support Russ Allbery
- Re: RFC 288 (v2) First-Class CGI Support Philip Newton
- Re: RFC 288 (v2) First-Class CGI Support iain truskett
- Re: RFC 288 (v2) First-Class CGI Support Nathan Wiger
- 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 Support Robert Mathews