Sounds like a job for IPC. Allowing any number of users to create an arbitrary number of files is a security hole. You'll need to come up with a better mechanism since anyone passing through could flood the server with requests and possibly pose a DoS attack on your filesystem. At least put a limit on how many file can be in existence at any point and time and block until this requirement is met (bad news for people waiting on one guy with a 28K modem...) The best solution would be to create some shared memory or use some other form of IPC where you can then alert the next cgi ("imagegenerator.cgi") what is going on. Minimally, you should be able to store the images (if not the relevant data) in the shared memory (or FIFO, if you prefer, though slower) and present a high-speed cache for your users to enjoy. You control over image production and deletion will be optimized and far easier to deal with. I really hope you're using CGI::Cache, a db level cache, or web server cacheing mechanism. The increase in performance may surprise you. Have fun!
AgentM Systems nor Nasca Enterprises nor Bone::Easy nor Macperl is responsible for the comments made by AgentM. Remember, you can build any logical system with NOR.

In reply to Re: deleting a file after loading by AgentM
in thread deleting a file after loading by belize

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.