Instead of making the user wait for the emails to finish, why not start a detached process to do the mailing and let the user go and look at the progress on a separate page ... or not, as, if and when he wants to review that progress. The detached program could record its progress in a file loaded up by the page where he can review that progress.

Update: Of course, even users expect that even when mail is sent it takes time to be received anyway. The delay between sending and receiving is all the user sees, so why bother to take your part of it out of the closet? It was only the making the user wait instead of detaching that made it seem (temporarily) attractive to do so.

One world, one people

In reply to Re: CGI progress indicator by anonymized user 468275
in thread CGI progress indicator by Anonymous Monk

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.