In answer to your first question, your file uploads are almost certainly arriving via STDIN, and the first time you new CGI, it reads all of STDIN. The second time you new CGI, there's nothing left on STDIN for it to read, so it doesn't see the file contents.

Besides STDIN, CGI also gets parameter information from %ENV (see perlvar), which doesn't change after being read.

In answer to your second question, you basically have to make sure to create only one CGI object, which every module will use. A simple singleton package can accomplish this:

package My::CGI; use CGI; my $cgi; sub cgi { $cgi ||= CGI->new(); return $cgi; } __END__ # use this way: use My::CGI; my $cgi = My::CGI->cgi();

In reply to Re: Question about the upload function in CGI.pm by kyle
in thread Question about the upload function in CGI.pm by technojosh

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.