Hi

I am currently playing around with Dancer2 and wonder about the proper way to start a long-running child-process.

But even though I currently use Dancer2 I guess my question is more about PSGI in general.

I don't know that much about it but my understanding is that PSGI/Plack abstracts away the deployment details, so in theory your PSGI application should not be affected regardless of whether the app is later deployed as GCI or running under starman or whatever, but I cannot see how you can abstract away all the mechanics of forking (e.g. what part of the system reaps the childs again etc).

So what is the best practice here?

Not forking at all and using some job-qeueue mechanism or dealing with it on a case-by-case basis as there is no abstraction for it?

Please enlighten me...


In reply to How to fork in PSGI/Dancer2 by morgon

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.