[SOLVED] should I run my Timer as a daemon?
I am using a Timer to compare the efficeincy of some algorithms and draw graphs of their relative performance across a range of inputs. Anyway needless to say I would like my Timer to be as light weight as possible, especially for the less processor intensive tasks so that there is a minimum of insertion error. I notice on the java Timer API there is an option in a constructor to run my Timer as a daemon. I know what daemons are in the context of system software and the API has this to say on the subject:
"By default, the task execution thread does not run as a daemon thread, so it is capable of keeping an application from terminating. If a caller wants to terminate a timer's task execution thread rapidly, the caller should invoke the timer's cancel method."
My question is: What is the difference between a daemon Timer and non-daemon Timer? Which (if either) is lighter weight? Is it simply that an executing daemon Timer will not prevent an application from terminating
PS. I'm new to this forum-posting lark. Have I posted an appropriate amount of information? Is it too much to read? I could have just said "Explain daemon timers plz?"