
Signature
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |
Hello,
> You don't say what your target OS is or if you want to write a OS you're
> running on or if you want to write something that's OS-agnostic so its
> difficult to give specific advice.
It is going to be MS Windows.
Regards, mark
Martin Gregorie - 01 Sep 2006 13:42 GMT
> Hello,
>
[quoted text clipped - 3 lines]
>
> It is going to be MS Windows.
Have you considered writing the application so it does the transfers you
need and then quits and running it under the control of the Windows
Scheduler?
Tis way you get a simple application and there's already a GUI (supplied
by MS) that can control when it gets run.

Signature
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |
Mark Space - 02 Sep 2006 19:01 GMT
> Hello,
>
[quoted text clipped - 5 lines]
>
> Regards, mark
Yes, ditto to what Martin said. Much better to use the OS features than
to try to do everything yourself.
On Windows 2000 (mine), there's a control panel for this:
Start->Programs->Accessories->System Tools->Scheduled Tasks
Encourage the user to place your app here. This provides effectively 0%
overhead, just like cron. I don't think there's any way you can provide
that. Just having the JVM up at all is a pretty large overhead, if it's
going to be doing nothing except expiring a counter every 24 hours.
Also, think about other paradigms. If you are updating another app,
consider having it check for updates whenever its run.