AM,

Kozz gives you something to chew on but there are other things you can consider.

Your user may be impatient if your cgi is taking a long time to return any data. Are you buffering all the output and sending it at once? Or are you doing a lot of processing before you spit out any html? You may want try and send out html early (and often), so the user has some clue things are going on (Kozz hit this with his fork idea and merlyn goes into more detail in one of his columns).

If it doesn't matter if the user hits the submit button many times, you may want to follow the "stop" techniques as outlined in Re: Detect Stop Button. This should ensure your cgi's die when no-one is listening anymore.

-derby

In reply to Re: Perl runs away.... by derby
in thread Perl runs away.... 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.