> like Holger already wrote I think there is no safe way to transport
arbitrary graphs over the wire
 
Hm, what do you mean by safe? 
There are many libraries that can safely serialize/deserialize Java object
graphs while correctly keeping references inside the serialized data. The
only additional thing needed in the serialization is a context that keeps a
list of all objects that are part of it. Why wouldn't this work in an OSGi
environment?
 
> Load balancing is an interesting question. CXF DOSGi does not handle this
itself.
 
Ok, thanks, so this means cooking your own stuff then.
 
And no MQ-like solutions for remote services, so JMS could be used for the
load-balancing?
Hm, this makes me think of EJB. Are there any OSGi-friendly EJB
implementations that could provide service access over JMS?
 
Best regards
Mike
 
Christian Schneider wrote:

Hi Mike,


I think almost all remoting solutions will require your data to be in a kind
a tree form. This can be considered a smell as it may require conversions
between your inner domain model which probably has cycles and the data sent
over the wires which may not have them.

In fact though like Holger already wrote I think there is no safe way to
transport arbitrary graphs over the wire. So you most probably will have to
cope with this.


Load balancing is an interesting question. CXF DOSGi does not handle this
itself. It will simply provide all available endpoints as OSGi services. So
this provides at least failover and you can add load balancing based on
these local services if you like.


Christian



2014-02-28 10:28 GMT+01:00 Mike Wilson <[email protected]>:



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.
 
DOSGi's distribution provider is based on SOAP so it seems this
implementation will limit the expressiveness in data transferred as
arguments and return values, such as duplicating objects that are referenced
more than once and not supporting cycles at all.
 
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?
 
Bonus question: What's a good setup for load balancing Remote Service calls
between multiple remote servers?
 
Thanks

Mike Wilson

_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev





-- 

-- 
Christian Schneider
http://www.liquid-reality.de
<https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&UR
L=http%3a%2f%2fwww.liquid-reality.de> 

Open Source Architect
http://www.talend.com
<https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&UR
L=http%3a%2f%2fwww.talend.com> 

_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to