On 28/02/14 09:54, Holger Hoffstätte wrote:
On 28.02.2014 10:28, Mike Wilson wrote:
We're doing remote calls between OSGi containers on different servers
and I'm looking at Remote Services to do the job. I've noticed that
Apache CXF/DOSGi http://cxf.apache.org/distributed-osgi is the reference
implementation.
Unfortunately it's effectively unmaintained, unfixable and full of bugs.
While I'm not actively invoked in this project, I'm finding the above
comment being negative and I'd say very far from the truth
Sergey
P.S. Sorry if it is off-topic
Can you recommend any Remote Service distribution provider
implementations that offer better support for keeping "referential
integrity" within the data transferred to the remote server?
I would love to hear what semantics of the consequently necessary
distributed GC you'd expect in the face of failures, netsplits and
stragglers. Once that is cleared up we can talk about why you think that
distributed globally consistent object networks with (almost guaranteed)
cycles are a good thing in reality to start with.
There's a reason (many actually) why nobody with half a brain (get it?!)
uses RMI any more.
Bonus question: What's a good setup for load balancing Remote Service
calls between multiple remote servers?
"For stateless or stateful services?" he asked, tongue in cheek.
In a nutshell: if you're looking for anything more than a
"network-transparent" extension of the Java method call semantics, you
are looking in the wrong place. Neither Java's (and hence OSGI's
service) method invocation model nor the RSA spec are expressive enough
for anything beyond that.
-h
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
