Cees de Groot says:
>>The Java threading model, as specified, is quite weak.
>Yep. Some prices have to be paid for WORA. Personally, I don't think
>it's a very big price.
It depends on what you're doing. In the current system, you can't even
really do applets correctly, because there's no way to stop them. You
basically can't control the thread behavior of any code, trusted or
untrusted.
I run a mailing list to work on these issues, taking a resource
accounting and control approach. http://gee.cs.oswego.edu/dl/javares/
[on priorities]
>>(the mechanism that's there does not work very well)
>I'm curious: "does not work very well" (current implementations) or
>"can not work very well" (the standard has problems) ?
Can not work very well. Priorities don't really mean anything in the
Java spec - it's not clear there's even a guarantee that a thread of
higher priority will execute preferentially to a thread of lower
priority. In practice this isn't a problem for me, but it seems really
weak.
Peter Schuller says:
>What about implementing a little scheduler in Java?
There's some nice examples of doing that, and it is an interesting
solution. It's a lot of work, though, and you still have the
fundamental limitations of the threading model. If you get something
working, release it open source and we'll all use it!
[EMAIL PROTECTED]
. . . . . . . . http://www.media.mit.edu/~nelson/
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
