[MUD-Dev] Re: [Java] multithreading: update and a question

[Chris Gray]

[Vadim Tkachenko:]

 >See, there's a drawback - the architecture solutions for one/one,
 >many/one and many/many are different. Java becomes a curse
 >portability-wise, because it's SUPPOSED to behave in the same way, but
 >depending on the platform implementation different people working on
 >different platforms will lose their (voice fibers? what's the English
 >term? am I making myself clear here?) shouting and trying to convince
 >each other in what sucks and what rules.
 >
 >The only portable solution I see so far is to have a java.lang.Thread
 >wrapper as a base of a thread entity, and make it just a thread for
 >many/many (also for many/one, because it doesn't matter in this case),
 >and something more sophisticated for one/one.

Ah, yes. As in the recent performance results for many threads on
various systems. (It's voice chords in English.)

If I'm not remembering wrong, Java does allow you to find out the machine
and OS you are running on. Is that how you plan to do things in your
wrappers? That should work out OK, but as you say, it sure isn't the
portable Java programming that we are supposed to have!

--
Chris Gray     cg at ami-cg.GraySage.Edmonton.AB.CA