Now if I can get my server push to work correctly.

Sorry, I can't help you there.

I don't see how the script can continue to send 'multipart/x-mixed-replace' content after it has closed the handles to get the webserver to let go? Thinking about it, I guess it might be possible to fool the webserver by duping STDOUT etc. before closing the originals. I haven't tried that, it just came to me.

I've been playing around with client pull for long running processes and found that the best way (on Win32) was to open a new socket, start a new process that inherits the open handles, redirect the browser to that new socket and have the original cgi script terminate. The spawned process then runs as a very limited html daemon responding to client pull requests on a thread with updated status information until the long running process has finished. I can then deliver the final status/output and die.

The thing I like about this is that it removes the client pull from the webserver, and also allows the long running process to detect if the client goes away, and terminate early if it does.

But take all that with a huge handful (bucketful) of salt because literally all I've done is play with it. I've never tried using it for real.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re^3: close STDOUT does not work, why? by BrowserUk
in thread close STDOUT does not work, why? 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.