Your english is perfectly understandable--and a lot better than my Russian :)

There are three problems with trying to help you:

1. The code you posted, and your description above, do not show or describe what you are actually trying to do. I would need a description something like:
   1. Read nnn urls from a file.
   2. Issue a HEAD request for each url.
   3. Extract the modified date/time (how?)
   4. Compare this against (what?).
   5. If the page has been modified then
      1. Issue a GET request for the url.
      2. Save the page? content? to a file named?
   6. While the worker threads are running, the main thread will wait? display status? process the retrieved content?
2. The first key rule to making effective use of iThreads is: "Only use a few!".

   Ithreads are relatively expensive to start and run and using more than 10 in any application is self-defeating. The time spent swapping between many threads negates most if not all of the benefits of using them.

   Using iThreads effectively, requires a different way of approaching the problem from either:

   • the fork approach exemplified by many *nix programs,
   • Or from the techniques used by C programs using "native threads" or most other forms of threading.

   Most of the documentation available for threading is not applicable or relevant for iThreading, and even that documentation available directly relating to iThreading is sadly lacking in depth and practical "How to..." advice.

   I've been trying to build up a body of practical examples that might form the basis of better documentation for a while, but the main problem is that all my experiments and programs are only applicable to Win32. Even when I have supplied example code to people to try on non-win32 platforms, I have never recieved any feedback as to whether it even works on their system. That makes drawing conclusions regarding the generality of the techniques I have developed almost impossible.

3. IThreads are only beneficial if the data being accumulated or processed within the threads requires collating, merging or otherwise cross-referencing.

   Unless you are going to use the results of the thread processing in some way that makes it beneficial to share those results--ie. something more than just logging them--then you are almost certainly better off using forking to achieve concurrency--at least on a non-Win32 platform(where fork is implemented using threads).

To summarise: Post your original code; and/or a full description of the problem you are trying to solve. I will then have a go at advising you on how best to tackle the problem with iThreads--or why iThreads are not applicable and advise what alternatives you might consider.