On 2/2/01 12:56 PM, "Peter Donald" <[EMAIL PROTECTED]> wrote:
> Consider the case of select() style functionality - why has not that been
> added. It's not because it isn't portable, nor is it because it is technically
> hard or a design challenge. I put it to you that the sole reason is because it
> would mean that low end servers with a small number of CPUs could actually
> start to compete with the suns network OS hardware which would be a bad thing
> for them. Yet not having this functionality has proved considerably
> challenging to anyone running java as server and in native threads mode. I
> suspect this will change with Merlin release as more people were allowed to
> have an opinion.
Oh this is just hilarious. Of course you aren't going to believe me since my
motives are always so "questionable", but the reason it's not there is
because the JDK team have been working through their queue of real problems
in the platform and this hasn't yet burbled to the top of their queue. It's
not that it's not a real problem, it is, but when you have finite resources
and need to structure them to get things done, triage results in things
dropping that are unfortunate.
Now, whether or not the model that is being used is efficient for getting
work done or an appropriate model is not something that I want to get into a
discussion on -- but I'm simply pointing out that you are ascribing to
malice something that isn't the result of malice.
.duncan
--
James Duncan Davidson [EMAIL PROTECTED]
!try; do()
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
