Hi!
I'd like some suggestions from more experienced programmers on how to do this the right way. Let me first make clear that I could do this on my own but I'd like the opinions of others to choose more specifically how to go about it.

What I need is for a program that is running on a server to write a report and send out by email upon a number of preset clock strikes scattered throughout the day at uneven intervals.

This might seem like a mundane enough task but I have yet to find a solution that doesn't feel awkward.

My current solution is a QList<QTimers> with timers that are initialized in the ctor of the program and are singleshot-started but it's rather bulky code and when the timeout-signal is shot the calling timer should simply be set to 24 hours (triggering the same time the day after) and then all is up'n'running but it feel like I'm overlooking some simpler solution?

It feels like a rather common behavior and I've gotten so used to the convenience of the Qt framework I'm actually half expecting there to be a QAlarmClock where I can just pass a QList of QTime's or QTimeDate's and, presto! =)

Any takers?
Thanks
/Tottish