My question is how do I make the design of this Windows Service clean...

By doing a good job :) That sounds flippant, but "clean" is such an 'airey-fairy' and subjective term that it is impossible to answer. What you, me and 10 others would call 'clean' are probably a dozen different things.

Is there some part of your app, which from the above seems well thought through, that you are having your doubts about your current implementation? Specific questions (with code) are generally easier to attempt good answers to.

... how do I share data between threads and packages?

Assuming you've seen threads::shared, what problems are you having? Again, specific examples and code are good idea.

Generally, share data not code. Objects contain both and do not easily move between threads.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re: Windows Services, Win32::Daemon, Threading, and SOAP::Lite by BrowserUk
in thread Windows Services, Win32::Daemon, Threading, and SOAP::Lite by hackdaddy

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.