+ + for your response... even though I still have some issues.
  1. You say "I am only concerned with having recv'd that majority of files as it generally guarantees that the rest will follow." My paranoia/pessimism (about the inclination of complicated processes to fail unexpectedly) tells me that if I don't have the whole package, I may not get it. OTOH, "...generally guarantees...." is likely a fair to good indicator if your "extensive historic data" allows you to infer a stage at which the feed is unlikely to fail.
  2. On the proverbial third hand, why mark a feed "completed" when it's not? You could just as well mark it "Lookin' good, so far at nn%" and report that to your ap. And, perhaps even better, you could also use your historic data to call attention to any feed that is failing to satisfy your "likely to succeed" criterion at some stage of reception.

    A notice that one has a potential problem is likely, IMO, to be more useful than a notice that says 'All's well on the Western Front."

GrandFather's approach should be easy to adapt to identifying likely failures.

In reply to Re^2: Calculating Completion of Feeds with Varying Volumes by ww
in thread Calculating Completion of Feeds with Varying Volumes by temporal

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.