It seems to me you have the biggest piece of the puzzle already. One way is to have a way of uniquely identifying each user; and to incorporate that unique identifier into the name of the file you save away. Since your users are authenticated before they ever get to see any content in the directory your CGI lives in, you *can* get the user's name at the time you generate the file in the first place, so this shouldn't be at all difficult.

If it's a function to get that name that you're looking for, CGI::remote_user()

My apologies if I'm missing something here.

Philosophy can be made out of anything. Or less -- Jerry A. Fodor

In reply to Re: Managing Concurrent CGI.pm Query Objects by arturo
in thread Managing Concurrent CGI.pm Query Objects by sierrathedog04

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.