In the above, something is just the name of the particular small piece of the larger task. The prepare_something/unprepare_something calls are there to avoid all possible side-effects in is_it_time_to_do_something. I would use before_something/after_something are there for things logging, timing, transactions and other "admin" actions that aren't related to something.

2014/04/09

Back in the mists of time, when the Web was young and unconquered, Lincoln Stein wrote a module for Perl that would allow people to easily deal with parameters handed to a CGI program and to generate HTML. This module eventually grew to include not one but several kitchen sinks. It includes its own autoload mechanism, it's own file handle class and more. It Just Works when called FastCGI, Perlex, mod_perl and others.

While CGIs have all but disappeared, this module is still very useful for handling all the finicky edge cases for dealing with HTTP request content. But if you write your own web server environment, using CGI.pm to parse the HTTP content can get be hard. You basically have to fake it out.

And here we parse the params from a POST request. Note that POST request can be big. Very big. If you aren't careful, they will fill up your memory.
Always check Content-Length before reading in a POST request. In the following code, all the content was written to a file.

About Me

I am a self-employed programmer. I program computers for a living. This also means I spend half my time as a sysadmin. The annoying half. I work nearly exclusively with Linux and Perl.
All this goes to say that NO, I WILL NOT HELP YOU FIX YOUR COMPUTER.