Here are some reasons to use ECF's OSGi 4.2 Remote Services implementation:
- Standards Compliant: It is fully compliant with the Remote Services standard. No lock-in...now and forever
- Asynchronous Remote Services: Unlike other implementations of this standard, right now it provides support for Asynchronous Remote Services
- Multi-Transport: Right now it supports multiple network discovery protocols (e.g. Zookeeper, DNS-SD, SLP, Zeroconf, static xml-file), and multiple distribution transports (e.g. r-OSGi, ECF generic, XMPP, JMS, Http/REST-based protocols, JavaGroups)
- Extensibility through Modularity: The open discovery and remote services APIs allow new discovery and distribution implementations to be substituted at will...proprietary or open...without requiring any additional work to support the OSGi standard
- Enterprise support: We are completing (for ECF 3.5) our implementation of the Remote Services Admin specification. The progress on this can be easily and publicly tracked...contributions, test/testing, and early uses are welcomed and encouraged.
- Open Community: ECF is not just open source, but also has a completely open, diverse, growing, active...and most importantly...a contributing community
- Open Process: We've moved to GIT, to make community support and contributions easier
- Multi-Framework: ECF remote services now runs on Felix (and probably other OSGi frameworks as well)
- Robustness through Community Usage
- Low-license fee: $0 :)