So first off, in general I think that if it works, it's good. Which is not to say it couldn't be better; but is fixing this worth your time?

GrandFather's right that it would be more natural to just spin up a new process upon need, rather than relying on something sitting in memory chewing up resources. Auxiliary concerns include do you need your "mighty agent" to have persistent memory? Do requested tasks need to be performed sequentially? Does ordering of those tasks matter? Are there security/permissions aspects to consider (i.e. does your "mighty agent" need greater permissions than your other agents?).


#11929 First ask yourself `How would I do this without a computer?' Then have the computer do it the same way.


In reply to Re: Constant SQL Querys to send "signals" by kennethk
in thread Constant SQL Querys to send "signals" by stewe

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.