Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "IPopo Compatible Providers"
(Added some details on iPOPO) |
|||
| Line 1: | Line 1: | ||
==Introduction== | ==Introduction== | ||
| − | [https://pypi.python.org/pypi/iPOPO | + | [https://pypi.python.org/pypi/iPOPO iPOPO/Pelix] is a Python project that aims to implement OSGi specifications. |
| + | It is a two-parts project: Pelix, the service layer, aiming to be close to OSGi; and iPOPO, an Inversion of Control, Service-Oriented Component Model inspired by [http://felix.apache.org/documentation/subprojects/apache-felix-ipojo.html iPOJO]. | ||
| + | The sources are available on [https://github.com/tcalmant/ipopo GitHub] | ||
| + | |||
| + | Currently, iPOPO has an home-brewed implementation of remote services, which is based on Multicast packets for discovery, and on JSON-RPC for transport. | ||
| + | A Java version of this implementation is available on [https://github.com/isandlaTech/cohorte-remote-services GitHub]. | ||
| + | Also, a draft of a tutorial about iPOPO remote services is available [https://ipopo.coderxpress.net/wiki/doku.php?id=ipopo:tutorials:remote_svc here]. | ||
| + | |||
| + | This sub-project aims to implement compatible providers to let Java and Python services communicate through ECF. | ||
The enhancement bug is [https://bugs.eclipse.org/bugs/show_bug.cgi?id=421558 here]. | The enhancement bug is [https://bugs.eclipse.org/bugs/show_bug.cgi?id=421558 here]. | ||
Latest revision as of 14:47, 12 November 2013
Introduction
iPOPO/Pelix is a Python project that aims to implement OSGi specifications. It is a two-parts project: Pelix, the service layer, aiming to be close to OSGi; and iPOPO, an Inversion of Control, Service-Oriented Component Model inspired by iPOJO. The sources are available on GitHub
Currently, iPOPO has an home-brewed implementation of remote services, which is based on Multicast packets for discovery, and on JSON-RPC for transport. A Java version of this implementation is available on GitHub. Also, a draft of a tutorial about iPOPO remote services is available here.
This sub-project aims to implement compatible providers to let Java and Python services communicate through ECF.
The enhancement bug is here.