This is to evenly distribute email messages from customer_service@fsdf.com to salesperson1, 2, 3 etc.

Looks to me like someone may have made a couple of (bad?) simplifying assumptions:

  1. That there will always be exactly 3 salespeople available to service requests
  2. That all customer service messages are equivalent in terms of complexity
  3. That each salesperson services equivalent requests at the same rate

The approach you're taking hard-codes these assumptions.

Wouldn't it be better to provide a queue that the salespeople could take the next request from? That would let the salespeople load balance amongst themselves, and would still provide management metrics (e.g., the rate at which different salespeople absorb requests).

In reply to Re: sequential file handling (again) by dws
in thread sequential file handling (again) by airblaine

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.