Thank you,
loosing the complete message store because of a hardware or software failure would be ok. Web users won't get status reports for completed jobs (but the final report is saved permanently anyway, they could look it up at any time) or "cancel this"-messages won't be processed and users would have to re-issue the cancel-request. Users might also not get search results but a error message instead - perfectly fine if something is broken (and also current procedure in case of database problems).
Messages shouldn't get lost as a planned design feature (or problem).

I'll take a look at both suggested solutions.

Try out Padre - the free Perl IDE and visit my blog's Perl section.

In reply to Re^2: Message transport via network by Sewi
in thread Message transport via network by Sewi

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.