We must remember always that accusation is not proof, and that conviction depends upon evidence and due process of law. We will not walk in fear - one, of another. We will not be driven by fear into an age of un-reason, if we dig deep in our history and our doctrine, and remember that we are not descended from fearful men; Not from men who feared to write, to speak, to associate, and to defend causes that were - for the moment - unpopular.
While a DTM is cool, perhaps I'm missing twhat this implementation brings to the table that isn't already available, say via JavaSpaces (which also has the added benefit of being "pull" based, leading to natural load balancing).
Well, in terms of codability, I would say the IBM solution is much easier to work with than the JINI stuff as it is less dependent on a service model and more of a large machine system. I have done a bit of work with Jini and JavaSpaces, and I like them, but there is a barrier to entry that takes a good bit to overcome.
It really has more to do with style. Its like why people much prefer Hibernate or Castor to the current CMP systems -- and why EJB3.0 is such a radical redesign. Technological superiority isn't always the winner where the rubber meets the road of people writing code. Code simplicity is something too.
Comments
RE: Distributed Threading from alphaWorks
mega pimp, now if i just had an application that actually needed distributed multi threading, hmmm, oh well.
RE: Distributed Threading from alphaWorks
While a DTM is cool, perhaps I'm missing twhat this implementation brings to the table that isn't already available, say via JavaSpaces (which also has the added benefit of being "pull" based, leading to natural load balancing).
RE: Distributed Threading from alphaWorks
hehe, I said twhat.
RE: Distributed Threading from alphaWorks
Well, in terms of codability, I would say the IBM solution is much easier to work with than the JINI stuff as it is less dependent on a service model and more of a large machine system. I have done a bit of work with Jini and JavaSpaces, and I like them, but there is a barrier to entry that takes a good bit to overcome.
RE: Distributed Threading from alphaWorks
Just and addendum ---
It really has more to do with style. Its like why people much prefer Hibernate or Castor to the current CMP systems -- and why EJB3.0 is such a radical redesign. Technological superiority isn't always the winner where the rubber meets the road of people writing code. Code simplicity is something too.