By jsugrue
via java.dzone.com
Published: Jun 16 2008 / 09:16
I've been an enthusiastic champion regarding the advent of OSGi as used for a Java-based enterprise computing modularity standard. However, I have a very definite compartmentalization in mind as to what role OSGi should play — I draw the line at a single running JVM instance. I don't want to use OSGi as a cornerstone for distributed computing modularity.
-
An interview with Roy Osherove author of "The Art of Unit Testing"
-
.NET Locking Performance
-
Impala 1.0 M3 (dynamic modules for Spring) released, with major web enhancements
-
Simple JQuery UID Plugin
-
Thoughts On Domain Validation - Part 1
-
Computers still not quite clever enough to fool humans, Turing Test shows
Comments
enewc replied ago:
I have often heard this concern, but it represents a complete misunderstanding of the work. No one is inventing any new distributed computing software. The effort is to standardize the way in which any existing distributed software system can be configured into an OSGi Framework.
It would be good for posters like this to check their information before posting something a negative comment on a misunderstanding.
rv49649 replied ago:
enewc is being rather disingenuous here - reading the eweek source article, which is amply quoted from in this posting so as to remove any ambiguity of interpretation, it's quite clear that the eweek article author had precisely the same understanding of Distributed OSGi. It's entirely clear that the purpose Distributed OSGi is to be an enabler for all of the practices that this article posting here advises against. There's no dodging of that point.
Voters For This Link (12)
Voters Against This Link (2)