Sorry for my English. My description is not clear. Let's see how it works.

1) 

                   +-------------------------------+
                   |  SERVER                       | 
+----+  Request    |  +----------+   +-----------+ |
|User|--------------->| Target   |-->|   Perl    | | 
|    |             |  | Embperl  |   |  class    | | 
|    |<---------------| script   |<--|           | |
+----+  Responce   |  +----------+   +-----------+ |
                   |                               |
                   +-------------------------------+
In this case, user'll see current page till then requested function returns results and new page will be generated. Because In Embperl 2 there is no way to flush buffers before everything is done - this is answer of Gerald Richter (man who develops Embperl).
So, I'd just want to display for the user some helpful message. 

                   +-------------------------------+
                   |  SERVER                       | 
+----+  Request    |  +----------+                 |
|    |--------------->|  Wait    |                 |
|USER|             |  |  page    |                 |
|    |<---------------|          |                 |
+----+  Responce   |  +----+-----+                 |
   ^     (wait)    |       | Redirect              | 
   |               |       v                       |  
   |               |  +----------+    +---------+  |
   |               |  |  Target  |--->| Perl    |  |
   +------------------| script   |<---| class   |  |
      Respoce      |  |          |    |         |  |
       (result)    |  +----------+    +---------+  |
                   +-------------------------------+
In this case, user calls wait page which display some message (and user can see it immediately because it's short request). Then wait page parses passed arguments, builds new request (target script name should be passed as argument) and does redirect to target script.
So, the user watches wait page message till then long running operation will be finished and result page will be generated.

~ Schiller

In reply to Re: Re: Watching long processes through HTTP by nite_man
in thread Watching long processes through HTTP by nite_man

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.