Should this be a Windows Service ? ... Or maybe the System Tray Icon should be one program, and the daemon be a service.

The primary criteria of whether a program should be a service or not is: Should the program continue to run when no one is logged in?

And that boils down to one of two possibilities: a) Does it need to be running 24/7 (or, at least whenever the system is powered on) in order to fulfill its function? or b) Does it continue to perform some useful function when there is no one logged on?

(Note: Waiting dormant for someone to log on so they do not have to type 'start xxx' does not qualify!)

Also note that it perfectly possible to start and stop services from the command line on windows. See net help start and net help stop.

From what you've written, it sounds like it could justify being a service, but that it does not really benefit from the addition of the taskbar icon.

If you can justify -- because of some or all of your target audiences expectations -- to have a gui way of starting and stopping the service (in addition to the browser interface), I'd suggest that you write that as a small, standalone application (that perhaps installs itself to the taskbar when minimised if it is really going to be used frequently enough to justify that occupation of system resources). This would be completely separate from the service itself and would be (initially) started from a normal start bar icon, (or from the command line) by the user when they deem it necessary.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re: Should this be a Windows Service ? by BrowserUk
in thread Should this be a Windows Service ? by hennesse

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.