By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,240 Members | 1,519 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,240 IT Pros & Developers. It's quick & easy.

One Windows service and lots of threads, or lots of Windows services and one thread ?

P: n/a

Our application needs to run a number of tasks in background - they are
generally functionally unrelated and do different things but essentially
they all run a particular process at (different) intervals as defined by the
user and stored in a scheduling database.

Seems to me I can either create one windows service which looks at the
scheduling database for each process and if needed to be run, kicks the
process off on it's own thread; or I can create an individual service for
each process which simply looks after that particular process and doesn't
need to worry about the other processes.

Are there any good references on how to approach this issue ?


Nov 20 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.