When I've done this, I just have the CGI interface gather parameters from the user and then set a flag of some sort (presence of a file, a database value, etc) indicating that the process is ready to go.

The main program is kicked off by cron (or task scheduler in Win32) and checks for whatever the flag is and runs with the supplied params if the flag is found. The main program logs its progress so the user can follow what's happening - presumably via another CGI interface.

If there's a requirement that parameters can change, just have the main program reread it's param whenever it finds they've changed.

In reply to Re: Managing a long running server side process using CGI by SheridanCat
in thread Managing a long running server side process using CGI by GrandFather

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.