on Jun 25th, 2009API Layering for Distributed OSGi

We’ve added to our distributed OSGi documentation (with examples+source) for ECF 3.0/Galileo:

• Distributed OSGi Services with ECF
• Getting Started with ECF’s RFC119 Implementation
• Getting Started Using the ECF Remote Services API

We have API layering so service programmers can choose the simplest appropriate mechanism for their system requirements, while still providing access to ‘lower-level’ concerns when necessary:

• failure handling
• synchronous vs. asynchronous remote method invocation
• serialization and wire protocol
• and so on…

If you have any questions or comments, please let us know on the ECF mailing list.

Related posts:

• Distributed OSGi EventAdmin Service
• Remote OSGi Declarative Services
• RFC 119 and ECF – part 3
• RFC 119 and ECF – Part 1
• RFC 119 and ECF – part 2

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

• Tweet

Tags: api, ecf, eclipse, equinox, OSGi, rfc119

One response so far Scott Lewis syndicate

One Response to “API Layering for Distributed OSGi”

1. Fabio says:

   November 22, 2010 at 17:08

   Hi Scott,

   First of all, congratulations on the work in the ECF/DOSGi project. I’ve read some of your posts here, but I could not find any related to the use of “intents”. Is the idea of intents currently supported by your implementation? Could you give any information about it? Could you please give me some information concerning authentication mechanisms that could be used in distributed scenarios?

   Thank you, very much!

   Best regards,

   Fabio