What I was asking wasn't a Perl question - it was CGI/design question
Many of this can be solved by widening your horizon, as some have already said. One way of doing that is using other programming languages, but every time I do that, I only get annoyed by the other language and wish it was more like Perl. My way of seeing things apart from each other is reading specifications.
Let's take CGI programming for example. We use http, so let's skim over its specification (rfc2068) and see what happens. In the abstract, it states that http is stateless. So we know our CGI script won't be running forever, but will handle only one request. It also mentiones headers, which is important: apparently headers are not a CGI-specific thing. So let's see what CGI is then. Using its specification, of course. It says some things about standard input and output, but Perl is never mentioned. Hey, CGI is not Perl-specific!
Reading non-Perl documentation is often a good way to know that some issue is not a Perl issue. When googling for information, try "-perl" to refuse all documents with "perl" in it, and see the other approaches.
- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.