Thanks, Niclas. I couldn't say this better. Just to add that it does so only for the classes that were used from the original service bundle. You can see this temporary bundle from a different perspective as a stripped version of the original bundle (minus everything that is not used by the service interface) plus that it has a special implementation of the service which happens to be a proxy object. I am currently working on provisioning bundles which happen to be dependencies of the original bundle to the clients, plus a distributed lifecycle management for those "satellites".
Cheers, Jan. ------------------------------------------------------------ MSc Jan S. Rellermeyer, Systems Group, Department of Computer Science, ETH Zurich IFW B 47.1, Haldeneggsteig 4, CH-8092 Zürich, Switzerland http://www.systems.ethz.ch <http://www.iks.inf.ethz.ch/> ------------------------------------------------------------ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Niclas Hedhman Sent: Mittwoch, 24. September 2008 12:59 To: OSGi Developer Mail List Subject: Re: [osgi-dev] Distributed OSGi On Wed, Sep 24, 2008 at 6:51 PM, Fredrik Alströmer <[EMAIL PROTECTED]> wrote: And could you please elaborate a bit? Maybe I get a little bit confused by your use of "proxy", I mean calling a method on proxy object, forwarding that call, executing it on the server, and transporting the return value back to client, that I understand. I don't get where the proxy bundle comes into play though. What use is a proxy bundle on the client? Or are you talking about distributing the necessary classes to interact with the proxy object? IIRC, R-OSGi collects all the classes needed on the deserialization side and creates a temporary bundle with those classes exported. Jan can elaborate... Cheers Niclas
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
