VM thread pool ( was: 3 questions)

[Clemens Eisserer]

> 3. I'm not sure I see the need for a new entry point - as long as these
> are always going to execute Java threads. You just need to turn the
> existing entry into a loop that will return to waiting when a
> logical-thread has completed - though some of the initialization done
> when a new thread is created will have to be moved to the thread itself
> as part of the entry logic. I don't see that you would want to "jump" to
> a new entry rather than just calling it and returning normally.

Well wouldn't it be great too if the thread-pool could be accessed
from native code too?
I just imagine that for some quite heavy, but "concurrent-ready" work
it would be maybe good to have such a system. I just imagine Java2D
where large workloads (e.g. interpolate large image, fill antialiased
path) could benefit from the additional processors available.

lg Clemens