Think about the Timer object as a single thread (unbounded) queue of TimerTask objects, meaning, only one timerTask can run at a time and the tasks are executed one after the other (let's ignore the schedule option for the moment).
If you would create a class which would extend the TimerTask and use to connect to your server, you can create multiple instances (preferably, create new instance on the on the end of the current instance run method) and execute them one after the other.
To use more than one thread, you would need to create another Timer object for each thread.
For summary:
1. Extend TimerTask and use this class to connect to a URL.
2. Make sure to create new instance only at the end of the run method.
3. Have a (synchronized) vector and a static counter that would keep track of the URL already read.
4. At the end of the run function check if you reached the end of the URL list. If not, create another instance of your class (see #1) and schedule it to run immediately.
5. Create Timer instances per the number of threads you would like to use (see cons).
Pros:
It might actually work and it uses a built-in API (less coding and usually better performance).
Cons:
You are limited to the number Timers that you can create (I think 5 for an application) and it's a bit of an abuse to the Timer mechanism.
Hope that helps,
E.
