"What's the recommended way to receive HTTP input on multiple channels, while abstracting away which channel(s) was used?" is, itself, a perfectly good question.

I have no idea why you're so hellbent on painting this as an XY problem. The OP needs to receive input. The OP is used to receiving it via CGI.pm. The OP understands that CGI.pm is deprecated and wants to know the current, non-deprecated alternative which comes closest to working in the same way.

None of that is application-dependent, nor does it suggest that there's a "real question" behind the question of "how do I accept user input?".

In reply to Re^4: CGI.pm not good practice, so what is good, modern, practice for reading CGI paramters? by dsheroh
in thread CGI.pm not good practice, so what is good, modern, practice for reading CGI paramters? by leszekdubiel

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.