I think this is how I'm going to solve this issue. Once I get some time to get back to it again.

Setup a table in a DB.
Fork off the process like I was originally going to.
The result set is stored in the DB. Or, a ref to it. Or something similar.
The script is sent an ID. Which is the KEY value to the DB the result sets are stored in.
First thing the script does is check for data in the result_set column, based apon the sent key.

Yes data, then the result set must be done. So spit_out_html();
No data, then the result set must not be done. Refresh and try again.
No Key. When it was never created. Go fork and create the key and refresh to wait for a result set.
Sound like a plan? We'll see what happens. I'll keep everybody updated on my solution.
Thank you for all the advice as well. Its been a big help.


_14k4 - webmaster@poorheart.com (www.poorheart.com)

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.