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 "ECF/Adopters"
< ECF
m (added the line about CoFFEE as ECF adopter) |
|||
| Line 8: | Line 8: | ||
* [http://www.remainsoftware.com Remain Software] uses the OSGi RFC 119 Remote services implementation | * [http://www.remainsoftware.com Remain Software] uses the OSGi RFC 119 Remote services implementation | ||
* [http://sourceforge.net/projects/coffee-soft/ CoFFEE] uses the ECF generic provider | * [http://sourceforge.net/projects/coffee-soft/ CoFFEE] uses the ECF generic provider | ||
| + | * [http://www.osgiliath.org/ OSGiLiath] Framework for Service Oriented Evolutionary Algorithms (uses ECF for communication) | ||
Latest revision as of 07:29, 5 July 2012
- Versant Corp for Vitness (mainly ECF discovery and UI)
- Cloudsmith Inc. for Buckminster.
- Eclipse Platform includes Equinox p2 which uses ECF for all network data transfer.
- IRC users on irc.freenode.net, #eclipse, #eclipse-dev, #eclipse-ecf and others use the KOS-MOS IRC bot, which was built using the ECF Bot Framework.
- The EPP project includes ECF in the RCP package
- The eConference project
- jACT-R, a cognitive simulation system is exploring ECF for distributed model execution
- Remain Software uses the OSGi RFC 119 Remote services implementation
- CoFFEE uses the ECF generic provider
- OSGiLiath Framework for Service Oriented Evolutionary Algorithms (uses ECF for communication)